This blue rectangle is fixed on the screen. Sometimes growing, shrinking and changing place.
tried the answer to this question:
In the Visual Studio SQL editor, how do I get rid of the boxes?
as I thought it might be related but didn't help.
How to get rid of it?
The box is drawn by Windows' Narrator feature for people with low vision. I recently accidentally toggled this myself by hitting winkey+enter. Hitting it again and moving the mouse cursor seems to toggle it back off again as well.
As mentioned below, depending on the narrator shortcuts configured on your system one of the following may work:
winkey+enter.
caps lock+esc
Full overview of narrator hot keys can be found here.
For some reason Winkey + Enter didn't work for me. However I found Caps Lock + Esc did the trick. See Narrator Shortcuts for more info
It looks like you have an extension installed which is adding that box. Try disabling extensions until you find the one that is causing this
Tools -> Options -> Extension Manager
There seems to be a a series of problems related to using the keyboard (only) on the mac - as opposed to resorting to the mouse. I am wondering if people have figured out workarounds for some of these issues.
Example 1: Hitting Enter does not work. Hitting tab does not work.Hitting space does not work. Only way to 'accept'/close the dialog is to mouse over and hit ok. Yuck.
Example 2: Using The Option button we can the "Do Refactor has D underlined - so clicking option-D should accept. However it does not work. Once again - only way is to click using the mouse
Example 3: In refactor dialog, one can not hit "return" or tab over or use "alt-r" to accept the Refactor. Once again - using mouse is the only way.
Example 4: In ANY open file dialog you have to type in manually the entire path. This one is confirmed bug by JetBrains, and I wonder if anyone has an idea of workaround
Click on the "option" key and the Mnemonics DO show up. I discovered this by accident.
I can't seem to find a question on this, but it might be because I'm unable to find a good way to search for it...
I recently updated my installation of Visual Studio 2010 Pro Power Tools, and now every time I type # in a code window, I get a search window of some sort opened instead of the # symbol in my code. I can't find the key setting that triggers this, and it's beginning to be a real problem.
I'm on a Swedish keyboard, so to get # I press Alt Gr+2. I've gone through all the settings under Tools/Options/Keyboard that starts with "View.", but found nothing.
Can anybody help me delete this keyboard mapping?
Update: I just realized that the key mapping Alt Gr+2 is equivalent to Ctrl+Alt+2. But I still can't find what it's mapped to...
I found the problem in the comment thread on the VS team blog post on the Solution Navigator - it turns out this problem is built-in into the extension, and they're working on fixing it for the next release. (Basically, they're binding stuff to Ctrl+2 and 2, but VS also takes the Ctrl+Alt equivalents, which then are interpreted as Alt Gr...)
For now, disabling Solution Navigator solves the problem (but, obviously, makes Solution Navigator unavailable...), but hopefully there will be a fix out pretty soon.
The VS2010 Power Tools provide functions to move lines up/down but I found these have stopped working. No amount of fiddling, reinstalling Power Tools, rebinding keystrokes, etc. has got them working again. Only after adding the Action.MoveUp and Action.MoveDown commands to my Edit | Advanced menu, where I thought I had seen them before, do I see that they are disabled.
What might disable these? How can I re-enable them?
I haven't figured out how to fix the individual problem but have done so by resetting my VS2010 settings to default.
I still have to use the VB6 IDE.
Unfortunately every time I start the IDE one of the buttons of the toolbar disappears. Almost always it's the Run button which goes first. Sometimes also items from the menu bar or the context menus are missing.
I have to reset the toolbars almost every time I start the IDE (Which is quite often during a typical work day). Recently I bought an IDE plugin which modifies the menu bar and requires a restart after every reset of the menu bar. (Otherwise it would crash)
I could live with just the resetting, but the restart is really annoying.
Is there something I can do?
To solve this problem:
Unload all add-ins.
Right-click on a toolbar and select the Customize... menu.
For each toolbar click the Reset... button (6 times in total).
Reload the add-ins.
For me action 3 was enough.
cf. MZTools faq (thanks to Andrea Bonafini), but these steps are originally from MSDN
It sounds like you recently bought a bad add-in. Can you get your money back? Every time I've had problems with disappearing controls in the IDE it has been due to a bad add-in. You can find out which one it is by disabling them, one by one, each time using the IDE for a while, then re-enable it and disable the next one, until the problem stops.
I still use one problematic add-in. It exhibits behavior similar to yours in that it makes the run button disappear. I avoid the problem by only loading the add-in when I need it, use it (it formats code), then I immediately unload it. If you don't use the functionality of the add-in that often, this could be an acceptable workaround.
Yea, i have this same problem with one of the add-in. But if you reset it. Shut the IDE down and open it back up again without doing anything, the IDE shouuld be able to retain the previous clean setup.
It's just guest, but:
Each graphical element on IDE (like button) is kind of resource (i.e. GDI handle).
Maybe your VB app doesn't manage these resources good enough and after sometime VB IDE cannot redraw elements like buttons (run is used often).
Also, maybe some IDE add-in is in conflict with some other add-in/application and breaks something -- I have this problem with Clip-X and MZ-Tools.
I had a similar problem when I was setting up the IDE to use for the first time, though it may not be helpful if you've been using the same IDE for a while. When I first started using the IDE, I would modify the toolbars and then close the IDE. When prompted if I wanted to save the open file I always said No, since the file was just a dummy file I was using to open the IDE with. Turns out the IDE was saving the toolbar preferences with that file, so they never got saved.
Try opening a file, customizing the UI, saving the file, then closing without modifying the code. This was the solution for me.
I've tracked down the problem and as suggested it was an add-in.
The problem went away as soon as I disabled the Visual Basic 6 Resource Editor.
How to restore your VB6 IDE without reinstalling:
Run Regedit
Find the entry for Visual Basic 6.0
Export your settings in case things
go wrong
Delete the 'UI' setting
Run VB and you will have your popup
menus back
The 'Find' button disappeared from my VB6 toolbar forcing me to select the Edit menu to use Find. I had two add-ins enabled: vbCodePrint and ResourceEditor; so I did away with both of them, turned VB6 off and back on, then put both add-ins back in and my button returned.
If you're still using the VB6 IDE, and I do amongst others, then this problem is not likely to have gone away. I use VB6 in Windows 10, and the problem is still there. But it doesn't affect me anymore.
I have had this problem a few years into using VB5 and VB6. Today, if I start VB6 directly, it may work fine the first time, but buttons will go missing the second time -- ALWAYS.
My solution, which I developed from day one:
Do whatever needs to be done to restore all your buttons. Save the Visual Basic 6.0 registry settings to a file, as suggested previously, and only keep the UI entry. Sometimes, you have to exit VB6 for it to post changes to the registry. So if this doesn't work the first time, try exiting before saving the settings.
I use my own program to launch VB6, which automatically copies my VB6 registry backup back into the registry -- by calling "RegEdit.exe /S D:\VB\IDE_Fix.reg" -- before I launch the IDE . This works every single time, and requires no action on my part.
If you read this, that means you are a programmer. You can make this work by yourself.
Mike
Reinstall,clean registry and update with SPacks etc....