|
jmoleary
Junior Member
USA
14 Posts |
 Posted - Apr 06 2022 : 2:20:47 PM
|
I'm writing code, adding a #include directive and I cannot stop VA from completing it incorrectly.
What I want to do is this:
#include <string>
As I am typing, VA has chosen an item in a suggestion list that is "string.h". That's not what I want but I've set VA to only commit on ENTER and TAB so I think I should be fine.
However as soon as I hit the '>' character, VA does select "string.h" and that's what I end up with
#include <string.h>
Not only have I been sure to only allow ENTER and TAB set as my commit characters in VA options, I have also removed *all* commit characters from Visual Studio's own completion characters.
I uploaded an image of the tooltip I see just before I hit '>'. It confirms that only ENTER and TAB are my commit options. I've also uploaded an image of my current VA options. Note that the tooltip is faded a bit (due to my screen snipping tool) but it's there
|
|
|
feline
Whole Tomato Software
United Kingdom
19024 Posts |
Posted - Apr 07 2022 : 06:42:16 AM
|
I am seeing the same effect here. Thank you for the clear description.
case=148033
I have been seeing the same thing here, but never really noticed it or thought about it, but yes, this listbox does seem to accept differently to other listboxes. Then again, it is listing different content, so in that specific sense it is "different". |
zen is the art of being at one with the two'ness |
 |
|
VA commits selection when when I don't want it to
