| T O P I C R E V I E W |
| IanB |
Posted - Oct 03 2024 : 07:58:17 AM
If I hit Ctrl+F and then type some text, the first character goes in the Find box but then focus is lost, and subsequent characters go in the file that is being edited.
I've had this issue since installing 2024.7. I've now downgraded back to 2024.6 and the issue has gone away.
Visual Studio 2022 v17.11.4 |
| 13 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Oct 15 2024 : 04:59:12 AM
2024.5 has a crash that effects some people. If you run into the crash, it can and does happen every few minutes, making it quite devastating. Having said that it only effected some people, other people never seemed to see the crash at all. But I believe this is why the download link was removed, since we don't want people downloading a version with a known crash bug.
Do you actually need to go to this version, and not a different one? VA 2530 avoids the CTRL-F focus bug, and is quite stable. |
| KRG |
Posted - Oct 14 2024 : 9:01:59 PM
Is there a reason that build 2024.5 is greyed out on the archive page? Do I need to roll back to 2024.4? Which iirc had other issues? |
| feline |
Posted - Oct 10 2024 : 11:03:25 AM
Thank you for the screen shot. For me, disabling the VA navigation bar is fixing the problem with the CTRL-F dialog. You still have the VA navigation bar enabled in this screen shot.
Hopefully we will have a fix soon. |
| azur |
Posted - Oct 10 2024 : 08:30:03 AM
Here is a screenshot if the focus would be lost. Maybe you can see what you have to turn on to get the issue.
Currently I have downgrade to VA_X_Setup2530_0.exe.
We have the issue with VA_X_Setup2535_0.exe.
|
| feline |
Posted - Oct 10 2024 : 08:06:06 AM
So far I cannot reproduce the loss of focus from the CTRL-F dialog with the VA navigation bar turned Off. I have spent several minutes typing all sorts of things into the Find dialog, some valid, some invalid. Typing speed in the dialog doesn't seem to matter.
I have made a note on the case about this happening though. But it does concern me that there might be another factor at work I haven't yet found. |
| Johan |
Posted - Oct 10 2024 : 06:02:39 AM
I got the navigation bar issue and disabled that but I still get the bug when I for example:
1. Select an inherited class in a .h-file.
2. Press Shift+Alt+G.
3. Press enter in the drop down to get to the .h file
4. Press Ctrl+f.
5. Start typing what to search for.
6. Notice that it automatically select the class name that it went to and your typing replaces it. |
| azur |
Posted - Oct 10 2024 : 05:31:23 AM
quote:
Originally posted by feline
That is unexpected! How often / easily are you seeing this? It looks like I didn't run enough Find's, since I didn't see that happening during my testing.
I have the same issue.
To me it looks like a timer is stealing the focus. Sometimes I can type multiple characters. Sometimes only one character. |
| feline |
Posted - Oct 10 2024 : 05:26:55 AM
That is unexpected! How often / easily are you seeing this? It looks like I didn't run enough Find's, since I didn't see that happening during my testing. |
| jschroedl |
Posted - Oct 09 2024 : 1:13:04 PM
Unfortunately, the workaround of disabling the navigation bar did not work for me. Focus still leaves the Find edit field randomly even with it disabled. |
| feline |
Posted - Oct 09 2024 : 12:10:04 PM
We are working on a fix, and are hoping to have an update with a fix out soon. I don't have an exact estimate yet, but as you are aware, this is very disruptive and thus urgent. |
| jschroedl |
Posted - Oct 09 2024 : 11:45:13 AM
Yeah, this needs a fix ASAP. Thanks for the partial workaround instead of disabling VA altogether. |
| feline |
Posted - Oct 04 2024 : 12:13:19 PM
For anyone else who runs into this, does turning Off:
VA Options -> Display -> Display VA Navigation Bar:
also fixes the problem for me. But obviously you loose the benefits of having this bar showing, including the Alt-M list. |
| feline |
Posted - Oct 03 2024 : 08:29:00 AM
Unfortunately this is a bug in the latest version. I have put in an urgent bug report for this, since this really is getting in the way:
case=165029
For now, if you use Ctrl-Shift-F for the full Find dialog, rather than Ctrl-F for the Quick Find dialog, this avoids the problem. You do then need to change the find scope to the current document to get the same result, but it is a work around for now. Obviously going back to the previous version also works to fix this. |
