Author |
Topic |
|
tjcbs
Tomato Guru
104 Posts |
Posted - Jan 16 2016 : 01:01:05 AM
|
This is one of my bigger peeves with VA: When the suggestion box pops up, I will often reflexively press enter, assuming that the prompted suggestion is the right one, only to have it suggest something obviously wrong. Here is an example:
Here, "capacity()" is the obviously correct choice, not "mCapacity". In addition, "mCapacity" is private, so it probably shouldn't be prompted at all.
VS 2013, VA 10.9.2068.0
Repro files available on request. |
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Jan 17 2016 : 06:14:03 AM
|
This is interesting, because it seems to be a VA member listbox or a suggestion listbox rather than the default Intellisense listbox which should appear here. First of all, I would like to ask: did you disable Intellisense?
Tools -> Options... -> Text Editor -> C/C++ -> Advanced -> Disable Intellisense or Tools -> Options... -> Text Editor -> C/C++ -> Advanced -> Disable Database
Just to know which direction should I go from here when trying to repro. |
Edited by - accord on Jan 17 2016 06:15:01 AM |
|
|
tjcbs
Tomato Guru
104 Posts |
Posted - Jan 19 2016 : 01:17:57 AM
|
Yes, Intellisense is disabled. |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Jan 19 2016 : 8:28:42 PM
|
We're considering better scoping (hiding items with hidden visibility, etc.)
case=24551 |
|
|
tjcbs
Tomato Guru
104 Posts |
Posted - Jan 20 2016 : 11:33:14 PM
|
Ok, but the main point is that "mCapacity" shouldn't be selected in any case, since it is not the best option. |
|
|
accord
Whole Tomato Software
United Kingdom
3287 Posts |
Posted - Jan 21 2016 : 1:21:52 PM
|
Which build of Visual Assist are you using? We have added case sensitivity when handling listboxes in 2086 via case=93633. |
|
|
tjcbs
Tomato Guru
104 Posts |
Posted - Jan 21 2016 : 9:21:09 PM
|
2068. But, this isn't a case-sensitivity issue, it is a different bug. "ca" was typed, so "mCapacity" should not be selected instead of "capacity". |
|
|
feline
Whole Tomato Software
United Kingdom
19022 Posts |
Posted - Jan 22 2016 : 9:46:11 PM
|
VA should be more case aware in VA 2086, so even with the private member being listed, "capacity" should be preferred. Using a simple test case here, "capacity" is being preferred for me, but that doesn't help you.
As a short term work around, can you please try turning Off:
VA Options -> Enhanced Listboxes -> Allow Acronyms and Shorthand
does this fix this specific case? It should, but even if this works, it may well cause more frustration than it fixes.
Do you see VA ignoring case a lot?
With this particular class, is VA suggesting the wrong item consistently, or is there a random element at work here? |
zen is the art of being at one with the two'ness |
|
|
|
Topic |
|