So I've seen a couple of questions about Visual Studio's Ctrl+Tab but none of them were referring to my problem
My Visual Studio will randomly start acting funny. Sometimes, when I hit on Ctrl+Tab to change tab, the navigation pane appears for half a second an disappears. If I hold Ctrl+Tab, it'll just appear and disappear constantly, disappearing too early to even switch one tab. When it disappears it gives the keyboard focus back to whichever document I was on (so no other program actually intercepts the focus)
Then it will randomly accept my Ctrl+Tab and stay on screen once every X tries for some reason.
I double-checked my Visual Studio parameters (which have never changed) and the shortcuts are correctly set: Ctrl+Tab to Window.NextDocumentWindowNav and Ctrl+Shift+Tab to Window.PreviousDocumentWindowNav. I try removing them and resetting them with no success.
Anyone ever had this problem? I don't know what is intercepting my Ctrl+Ctrl+Tab. When I restart Visual Studio, it'll work fine again for a while until at some point Ctrl+Tab messes up again for no reason.
Anyone ever had this bug? Any tips on how to figure out what it's from and how to fix it? I'm on Visual Studio 2013. If it's any help, I also have Resharper 8.2.1 with it
Thanks!
EDIT
A few extra details:
Disabling Resharper doesn't remove the problem, still happens
I tried setting the NextDocumentPaneNav shortcut to another combination, bug still happened
So basically it's not another running program catching Ctrl+tab for some reason, it's literally Visual Studio not willing to show the navigation pane for more than a micro second
Related
This is not a coding question, this is a problem I frequently encounter in the Visual Studio IDE. My mouse clicks are often ignored if I work fast. Usually it happens when I click on a variable name, the studio starts loading a tooltip or a highlighter for that variable and I immediately click on another variable or any other place in the editor window - the click will be ignored. Has anyone experienced anything like this?
This started happening around 2 years ago, don't remember exactly when, but it was right after a new version of the Studio was released.
By default, Visual Studio 2012, and others possibly, deletes an enabled breakpoint upon clicking it. This to me feels unnatural because clicking a disabled breakpoint enables it. Why then would a subsequent click delete it? I would expect the opposite, which is disabling the breakpoint, similar behaviour to Xcode.
Is there a setting somewhere that allows me to modify this behaviour, to clicking to toggle between enabled and disabled?
i don't know about a setting to change the single click behavior, but a little experimenting revealed that shift clicking the breakpoint disables instead of deletes it. this is in visual studio 2019. i found your question because i was wondering the same thing.
I am having an issue within the razor view in Visual Studio 2012. For some reason, most of the time when I am trying to edit a style property, my keyboard freezes and doesn't allow me to type anything.
<section style="height: 15[Try to edit here]">
For instance, trying to add in a zero or 'px' where the "Try to edit here" has been placed above is impossible as the keyboard freezes.
I have ReSharper 7.1 installed, I'm not sure if that is the culprit?
Closing the tab and re-opening it fixes the issue, but it then re-occurs later on (not sure if there is a pattern as to when it re-occurs)
This happens to me often. I just switch tabs and come back and it doesn't happen(for sometime of course :-)). It could be some kind of unresolvable bug although i would suggest that you uninstall ReSharper and try again to see if it gets fixed.
It happens to me and my other colleagues as well.
I have found it to be linked to having a floating code window(s). Unlike the floating window for something like Find Results (without a title bar), these appear almost like another instance of Visual Studio. These do not come to the front when the main Visual Studio Window is selected. I have found the keyboard stops responding only on these windows if there is a Find Results kind of floating window open. When the problem occurs, clicking on another VS window and come back sorts it.
In earlier versions of VS, any pulled code windows appeared without a thick title bar and window controls box.
I tried posting images of the two kinds of floating windows but don't have enough reputation to do so! Let me know if it is confusing and I'll try to clarify.
This may not be the only way for this problem to occur but this is what I've observed consistently in the last few weeks of using Visual Studio 2012. I have C# environment settings with Resharper 7 and Reflector installed.
It's basically in the title.
Whenever you "select all" in the Visual Studio code editor, the editor will scroll down to the bottom of the file. Is there a way to prevent this?
I'm using Visual Studio 2008 at the moment, but this applies to all versions.
No, you cannot change this behavior.
Microsoft has been aware of this since at least VS 2010, but either doesn't think it's a bug or doesn't think it's important enough to fix.
From their response to a 2010 bug report filed on the issue:
We unfortunately do not plan to change Ctrl+A's scrolling at this
time, so we're unfortunately resolving this issue as Won't Fix for VS
2010. However, it will remain in our database to be revisited for a future release of Visual Studio.
Source: Microsoft Connect
A quick Ctrl-Z-Ctrl-Y will get you back to where you were. If you tend to do a Ctrl-S Ctrl-A Ctrl-C a lot then just get used to this whole chain instead: Ctrl-SACZY. Or, create a macro: https://msdn.microsoft.com/en-us/library/a0003t62%28v=vs.90%29.aspx
I was struggling with this myself, but the "undo" suggestion gave me an idea and I feel kinda dumb for not thinking of it earlier. Visual Studio includes "Navigate Backwards" and "Navigate Forwards" buttons (CTRL-, and CTRL+, respectively). So after you finish selecting and copying, simple click the navigate backwards button or type CTRL- and voilà! you're back where you were.
I know it doesn't stop the scroll to begin with, but at least it puts your cursor back exactly where you left it!
In VS2010 when my intellisense (for C#) pops up the first selected item is not highlighted. This means i have to press down/up-arrow before i press dot/enter/parenthesis to get the full word.
This only happens with the new intellisense (the one that searches everywhere and not only in the beginning).
Also, how do i switch between the old and new intellisense? This seems to happen automatically sometimes so i guess there's some hotkey i keep pressing all the time without knowing.
You can go to Edit -> IntelliSense -> Toggle Completion Mode. I thought there was a keyboard shortcut for it, but it appears not on my current installation... that may be a side-effect of installing ReSharper though. You can always set a shortcut if you want one, of course.