Working in Visual Studio 2010 Express (C#):
Once I've switched the cursor to 'WaitCursor' in the pulldown menu, I can't change it to anything else. It seems like a bug to me. Can anyone else reproduce this? I did run a debug once or twice before trying to change the cursor again. Or am I missing something?
Had the same problem, solution was embarrassingly simple, yet infuriating. There's another property called UseWaitCursor. If this is set to true (as mine was, accidentally), you are unable to change the Cursor property to anything other than WaitCursor.
If someone can explain why there are two separate properties for setting the cursor, I'm sure we'd all love to hear it.
There is a usewait cursor property you need to set it to false in vs2010
I had this problem with the context menu on a datagridview. I was setting UseWaitCursor on the form to true and then to false after everything loaded. The context menu continued to show WaitCursor. I ended up setting the UseWaitCursor = false on the actual context menu after the load a
Related
Edit: I see "Silverlight -" is in front of my question, which I realize may have something to do with the alphabetical order of my tabs... really Visual Studio 2013 should be in front, anyone know if that can be changed?
I've been using the newer Visual Studio 2013 for about a week now, and I've found some quirks with it. The one that seems to happen the most is when I'm in the XAML editor working on something, suddenly if I go over to the property window I can't enter anything. I'm not running/debugging. I can type stuff in the regular XAML code editor window.
Even stranger, one of the times, I could get the cursors to appear in the fields. I typed a bunch of junk and just one character from what I types appeared. Another time I couldn't enter values into the properties, but I could double click on an event in the events window and create a new event handler. Just a minute ago I had the opposite, where I couldn't double click in the events window.
I think VS 2013 introduced async handling of more things, could it be related to that? Or perhaps because I'm using Silverlight? Right now my only workaround is to restart VS, does anyone have any knowledge about this? Anyone else experienced this?
I'm going to submit a bug report, but it would be a while before there's a patch, so I'm wondering if maybe someone understand the problem better and has a workaround? Or maybe just confirm that this exists and that I'm not crazy/my computer's haunted.
Edit:
I should mention another weird thing that happened two nights ago. I thought it was some how my doing, but I never figured out how I could have managed it without noticing. I was working on a piece of code, went to run after changing a few lines, and suddenly I had a ton of compiler errors. I go over to a user control I haven't touched in hours and suddenly the main LayoutRoot grid is completely empty. Luckily I'd committed to source control, but still...
I found an easy way to deal with this problem. It happens a lot after debugging so what I did was I created a batch file on my desktop containing this line taskkill /f /im XDesProc.exe and I run it every time the properties start misbehaving. Its the quickest way to reload the designer's functionality. I submitted this bug to microsoft they claim it will be included in the next update.
Me and another guy are developing a silverlight app and having the same exact problem. I accidentally found where the bug lies and how to mess with it to allow you to type "very briefly". Apparently this has something to do with tooltips. If you hover over anything in the property window when this bug is happening and allow a tooltip to popup while your cursor is blinking in a field, for the duration that the tooltip is up you can resume typing normal. As soon as the tooltip times out and disappears you can't type. So the only way you can edit or search properties is while a mouse tooltip is floating active. Very unusual. Can't seem to find any kind of tooltip settings in the program and the situation is very hard to find on google because search results assume your talking about programming tooltips. As far as I know we have had this issue since before release candidate. We are currently on official update 1 with the same problem persisting.
I am facing something strange in my Visio Add-in:
I have a CommandBar, with CommandButtons on it and I just launch my debug mode.
The first page is OK (the start page of Visio) but if I open a file or create a new file, I can click all I want on my buttons, nothing is working !
It worked perfectly on the start page but not on my new visio file...
I tried to comment parts of my code, but the issue seems to come from nowhere... I really do not understand.
If someone already faced this kind of behaviour, please help, I just do not know what to do...
You could try setting ".Tag" property for your button to some unique value.
More info here:
http://msdn.microsoft.com/en-us/library/aa201791.aspx,
"Maintaining references to command bar controls when contexts change"
There it is! A BUG in Visual Basic Express 2010:
I have several ToolStrip controls docked within several panels of a tabPanel.
And sometimes, some toolstrip disappear from the design page.
Still exists since I can see its name in the bottom under the design surface.
If I click that name, kazaaaaam!!!, if shows back, but if I click another control elsewhere it vanishes again.
And after compiling and running the project, user can't see it neither.
Only solution is insert a fresh new toolstrip and copy/paste the bad one's buttons!
Any clue?
There appears to be a weird bug in VS2008 and VS2010. For some reason it sets the .Visible property to False. If you go to the Properties section of your Project, select the ToolStrip and then set the .Visible property to True, it should work.
This is probably a really dumb question but i'll ask anyway.
I was wondering if there was any reason as to why a form wouldn't display its code when i click "view code" from the right click context menu in vb6?
It was working awhile ago so i'm kind of stumped.
Thanks
If forms are still not visible, try Window -> Cascade - This was the way I goit my forms visible again.
Maybe it is being displayed under something else. Check under the Window menu. Do you see it there?
Does the form display if you right click and select 'View Object'? If so, try double clicking on the form - that should display the source. You might also check the permissions to the file.
This is an old question, but since it's the first link retuned by a Google search, answering here may help many people.
Like someone else said, Window/Cascade does the trick, but with time it becomes annoying.
I have the same problem on my laptop with an external display. Closing the laptop cover (thus going back to only one display) fixes the issue.
An alternate way is to display the VB6 IDE on the main display (your main display is the one with icons on the bottom right corner). You can set your main display under System Preferences/Displays. There's a checkbox called "make this one the main display", it does not need to be your monitor #1.
Problem does not seem to occur if you have 2 displays side-by-side. Also, the fact that my laptop's resolution is not the same as the external display's resolution may cause the issue.
After taking these steps, you may have to restart the VB6 IDE to fix the issue.
Here's what I did:
Right-clicked on an item in the 'Objects and Timeline' panel.
Selected 'View XAML'
Resized the window to a '0' size so that it went off the bottom of the screen.
Now, even if I:
Select 'Reset Current Workspace'...
Or restart Microsoft Expression Blend....
I can't get the XAML view back.
Can anyone help me?
An answer from Unni, a PM on Blend:
I think this is a bug we have fixed
for Blend 4.
For Blend 3, the only workaround I can
think of is the following: go to the
equivalent of this folder on you
computer and delete user.config.
WARNING: Do so will get rid of your
settings and hence you might be
annoyed by a few dialogs etc. that you
had previously suppressed.
C:\Users\username\AppData\Roaming\Microsoft\Expression\Blend3
To be safe, I would copy the file
elsewhere before renaming so you could
replace it if that did not work out
for whatever reason.
THanks,
Unni