Ctrl-F (Find) often does not capture the first keystroke

Ctrl-F (Find) often does not capture the first keystroke by small_mountain_0705

Closed

Type:	Bug
ID:	778803
Opened:	2/7/2013 6:30:18 PM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

For years, when I've wanted to search for something in the Visual Studio editor, I have hit Ctrl+F (to bring up the Find dialog) and then immediately, without waiting for the Find dialog to come up, I've started typing what I wanted to search for. It didn't matter if it took a second or two for the Find dialog to come up; without fail, all of the keystrokes I typed after Ctrl+F found their way to the Find: box on the Find dialog.

Now, enter Visual Studio 2012, where Find is no longer a dialog box, it's just that little window in the upper-right corner. That's fine, except that now, when I hit Ctrl+F and start typing, the first key I type after Ctrl+F quite often goes into the editor window instead of into the Find box. This is incredibly annoying, on two fronts: First, I'm looking for the wrong thing, and second, I end up with all these stray characters scattered all over my source code. So my I start seeing red squigglies I don't understand, and then when I go to built, I get these compile errors caused by these stray characters.

This is a regression.

The characteristic whereby all of the characters you type after Ctrl+F were guaranteed to wind up in the Find box needs to be restored in Visual Studio 2012.

Details (expand)

Visual Studio 2012

In the Visual C++ editor (I do mostly C++ code, if it matters), hit Ctrl+F and immediately begin typing the word you want to find. The first character may go into the editor instead of the find box.

English

Windows 7 SP1

English

The first character of the search word ends up in the editor.

All characters you type after Ctrl+F end up in the Find box.

0 attachments

Posted by Microsoft on 2/25/2013 at 7:21 AM

Hello,
Thank you for logging this issue. The root cause is that the Find control is an Editor adornment. This causes some timing issues where the keystroke goes to the Editor before the Find control has a chance to appear on screen. We will continue to improve the Find experience in Visual Studio for future versions. I am marking this bug as copied to our backlog.

Thanks,
Murali
Murali Krishna Hosabettu Kamalesha | Program Manager | Visual Studio Professional - Editor team

Posted by small_mountain_0705 on 2/13/2013 at 12:35 PM

After I wrote this up, I started paying closer attention to see if I could identify scenarios that made this more likely to occur, to help you reproduce it. For a day or two, I wasn't seeing it happen at all and wondered if I was confused about it. But then, a minute ago, it happened clear as a bell. The scenario was, I had a floating editor window on one monitor and my normal docked editor windows in VS on the other monitor. Focus was in the floating editor window, *and* the Find box was active in the floating editor window. I clicked over in the docked editor window, immediately hit Ctrl+F and immediately started typing "sqlcondition". "sql" ended up going into the editor window and "condition" ended up in the Find box. Switching from the floating window to the docked window makes this pretty easy to reproduce.

Posted by Microsoft on 2/11/2013 at 12:56 AM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 2/7/2013 at 6:50 PM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)