Posted - Sep 02 2021 : 06:20:14 AM
| This seems to be a VisualAssist problem, not a Visual Studio 2022 preview. When I start the IDE with devenv.exe /safemode to disable all extensions, this problem goes away. The only extension I have installed is VisualAssist. This is with all the lastest versions (VS 2022 Preview 3.1 and the most recent VAssist build).
Pressing Ctrl+I opens the ‘find’ box and immediately starts searching.
This works fine for the first three, four or five characters, but then it leaves search mode and the next characters immediately delete the selection and start typing.
It is as if a timeout for IncrementalSearch has expired and IncrementalSearch is deactivated - but only momentarily. If I wait one or two seconds after the fourth character and continue typing, IncrementalSearch continues searching.
As if I was typing “too fast” for IncrementalSearch.
Or, to put it the other way round: IncrementalSearch works only if I type slowly. One character per second. If I type faster, the characters do not go to IncrementalSearch, but replace the selection in the editor instead.
Perhaps two different mechanisms fight for the character input?
Probably connected is the following issue: F4 does not work as it should.
When I "find all references" or compile and view the list of errors or the output, pressing F4 should jump to the next entry. Problem is, when I press F4 once, it _does_ jump to the next entry but somehow focuses on the editor now. Pressing F4 again does not do anything - until I click on the output/error list/find references panel first.