Using ext.net, the split-button control will add multiple menu items after each reload. I can't seem to figure out how to prevent this from happening.
When copying controls into Visual Studio, the IDE will always add auto generated ID's. This causes issues sometimes, remove the auto generated ID's and this should fix the issue.
Related
When creating an Excel file in Office365 including macros that increase and decrease value in a cell depending if you click up or down arrow causes issues when the sheet isn't perfectly aligned with the rows. This has been verified by Microsoft in case 34137940 as a bug - who suggested to ask the question here and reach out to a developer support team member. The problem is that no matter if I click up or down when a row is "visually splitted" the amount increases in the cell.
So what can I do to make this work as intended? I don't want to wait until Microsoft pushes an update. There has to be a solution for me to be able to disable smooth-scrolling somehow?
There is a temporary solution here to solve this by running the below commands to revert to earlier update - but that is not an option in this case since newer features is used as well.
cd %programfiles%\Common Files\Microsoft Shared\ClickToRun\
OfficeC2RClient.exe /update user updatetoversion=16.0.14701.20262
I also tried disabling smooth scrolling in Windows 10 (Link), following the below steps - with no success.
Navigate to System Properties by right clicking **Properties **from my computer.
Click on Advanced and click on Performance settings.
In Visual Effects tab of Performance Options window, click Custom. Then deselect the following items to Disable some unnecessary eye candy:
Uncheck Smooth-scroll list boxes.
I'm currently using Xamarin Studio and have a comfortable enough setup so that I can put my various pads (output, unit tests, solution tree, etc.) on different screens. I like it and I'd like it to stay the same wether I'm debugging, running tests or coding.
But right now, xamarin studio handles it himself and switches to the Debug view layout when debugging, which changes everything to their default (since I've never really changed it).
Is it possible to tell Xamarin Studio to either :
- Never switch layouts?
- Set which layout is used for each situation (and I would just use my custom layout)
I've tried deleting all layouts and XS just recreates them. No dice here.
I've tried switching to my layout when debugging, hoping it would remember "this is my debug layout now". No chance either.
And I'm hoping I won't have to change each separate layout, because first it'll take a stupid amount of time, and also because if I ever decide to make a change, i'd have to set it up over 5 different view layouts which is just ridiculous.
Note : I'm using the latest version of Xamarin of the stable channel.
So, does anyone know a way to keep one single layout for all situations?
Unfortunately, no, it is not possible with the current version of Xamarin Studio.
I read through both the preferences as well as the documentation. I even tried to create my own custom layout by navigating to "View" -> "Save Current Layout". Then I selected my new custom layout when I started a debugging session, hoping it would persist to the next one. But alas, the "Debug" view was chosen automatically.
This would probably be something you could bring forth as a suggestion of improvement to the Xamarin team. You can do so using their bugzilla.
I have been working for a few days now making a simple web page to be a basic cv/bio. I started by making my headers for the page and some simple animations when switching window sizes. After playing with adding some different colors in, I noticed that an asset I added, wasn't transparent(as I had intended it to be).
That said, I have tried to delete the item from the assets Library to no avail. I've tried removing all relevant keyframes, as well as trying to delete it from the Master Rules. The program will not allow me to delete the item, except from the Library, which does not affect the item on the page whatsoever.
I may well be missing something completely obvious and shall feel a fool when this is answered. Thank you for your help in advance!
To delete a layer, click on it in the timeline so that it's highlighted and then press the Delete key on your keyboard.
If the element is an asset imported by you, for example a picture, you must select it at the library collapsible menu and click the trash. If you can't find this menu, clic on Menu > Window > Library.
On Responsive window, click Edit base document. You can now delete it.
I have a problem with Domino Designer since the problem occurs not only in existing xpage and databases, it also happens in newly created databasen and xpages as well as custom controls.
The problem is that when I try to open an xpage or custom control, I will not se any code, or anything but an emppty blank page under the toolbars.
First I thought it could be my screen, then I thought it could be an configuration problem so I reconfigured the notes client and tried again, then I check if I could open the custom controls with the xml editor instead of the xsp editor, and that worked, but I want the xsp editor back.
What is this, a blank page, it seems that it could not render properly, because if I use my keyboard and pressing the space bar, then it ask me if I want to save the changes when closing the custom control by the esc.
Do I have to re-install the client? Or does it exist any configurations for the xsp editor I miss?
BTW, It happens the other day, and when I re-configured my installation it worked, but this time it does not.
Are you looking at the design pane and not the source pane? At the bottom of the blank page, above the properties area there are two tabs, click on the "source" tab.
If that's not the issue, I'm not sure what's going wrong
I did not have time to investigate any further, it must have been the render function of the XSP Editor that was corrupt, stopped working and I re-installed the Notes and Designer and then I could continue working. No problems in my code. :-)
I'm using the Ribbon control located on CodePlex, and following the tutorial located here . Once I add the reference, and the proper code in the designer I get this error when I try to view the form:
Exception of type 'System.ComponentModel.Design.ExceptionCollection' was thrown
And I cant figure out what I'm doing wrong. Anyone worked with this control and know how to resolve this issue?
Interesting; I just ran into this same issue with one of my own forms; which is how I found your relevant and recent question.
Here's how I solved it:
Open two instances of Visual Studio. Open the same project in both.
In one instance, goto Debug->Exceptions and enable all the 'Thrown' options to stop at first chance exceptions. This will stop the debugger when the exception is generated.
In the same instance, select Debug->Attach to Process, select devenv.exe.
In the other instance, open the form to cause the exception
With any luck the first instance should stop somewhere that yields a more relevant exception.
In my case it turned out to be something that I should have conditioned with:
if (!DesignMode)
{
// Do something that should only happen at runtime
}
Don't forget turn turn off all those 'Thrown' options later.
A workaround for me was:
Right-click on the form and 'View Code'
Keep the code loaded in the editor and then attempt to view the designer again.
This feels very glitchy and I cannot confirm whether it's a problem with my code (as I'm working on an entirely new codebase) or whether it's a VS2012 bug. If I find out, I will report back.
Since the solution outlined by pilotcam didn't work for me, I took a different approach:
Make a SVN commit for the file.
Open the “*.designer.cs” file of the form that shows the error in source view.
Remove larger blocks of form element declarations.
Fix all compilation errors with ReSharper (i.e. ensure that nothing is red anymore on the side-indicator).
Save the file. No need to compile.
Open the Windows Forms Designer of the form.
If the error still shows up, do a SVN revert to go back to the initial state.
Repeat steps 2 to 7 until the error does not show up anymore.
Now you’ve encircled the erroneous child control that causes the error.
Repeat steps 2 to 7 with a smaller amount of controls you remove, until you have only one control left.
In my case it was a user control inside a group control inside a tab control, so I first identified the tab control, then the group control and then the user control.
You could isolate the user control inside a new form to further investigate. In my case it was rather easy; I put checks for design mode around most of the functions inside my control to ensure the code only gets executed if the control is not in design mode.
This fixed my error.
I had the same issue and none of the above answers solved the problem.
At the end, emptying the "bin" folder and rebuild has worked for me.
Let me add two more cases when such exception can happen, along with when control tries to do something that is not allowed under design mode:
When it's impossible to compile the user control.
When designer code contains multiple similar (or identical) lines with initialization of same controls or properties, this can easily happen on merge.
All that cases produce same extremely meaningful error message, and in this particular two debugging of Visual Studio won't help, so I just ended up with bisecting my designer code.
[ReadOnly(true)]
[Browsable(false)]
Above all properties worked for me