Author |
Topic |
|
foxmuldr
Tomato Guru
USA
412 Posts |
Posted - Mar 27 2024 : 4:42:43 PM
|
I have a structure like this:
struct SHwnd
{
bool lDeleted;
bool lChanged;
bool lNew;
bool lDisplayed;
union
{
HWND hwnd;
int _hwnd;
};
};
When I'm in the editor, and I type something like:
SHwnd* p = /* code to create a valid instance here*/;
GetWindowLong(h->hwnd,
When I type the comma it's replacing the "h->hwnd" I typed in with the one lingering auto-suggestion which remains above like the attached images.
Is there a way to get it to not do that if what I've typed in fully matches another member's name? This is happening in Visual Studio 2022 in VAX version:
License: Standard ... Support ends 2025.03.27 VA_X64.dll file version 10.9.2515.0 built 2024.03.14 DevEnv.exe version 17.9.34723.18 Professional msenv.dll version 17.0.34714.143 Comctl32.dll version 6.10.19041.3636 Windows 10 10.0 22H2 Build 19045.4170 8 processors (x86-64) Language info: 1252, 0x409
-- Rick C. Hodgin
First letter typed:
Two or more letters typed:
After the whole word is typed, and comma is typed:
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Mar 28 2024 : 07:23:51 AM
|
No sign of this on my first quick and simple test, so trying a "better" test. But what bothers me here is that the "hwnd" item disappears from the listbox when you filter it with "h"
If you correct the code, what, if anything, is shown in VA's context and definition fields when you place the caret into "hwnd"? What happens when you press Alt-G? If you go back to the pointer, and use Alt-Shift-G and then show the members of this type, is "hwnd" shown?
I am trying to work out if this is a listbox filtering problem, or if for some reason VA doesn't accept that the struct contains the "hwnd" member. |
zen is the art of being at one with the two'ness |
|
|
foxmuldr
Tomato Guru
USA
412 Posts |
Posted - Mar 28 2024 : 10:26:29 AM
|
When I hover over the "hwnd" in the "h->hwnd" text, I see this:
When I press Alt-G it takes me here:
It all works. Shift-Alt-F and Shift-Alt-R do what they should. It seems like it's just that auto-complete list.
-- Rick C. Hodgin
|
Edited by - foxmuldr on Mar 28 2024 10:27:19 AM |
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Mar 29 2024 : 08:34:17 AM
|
Even with a better test case, I am not getting the * icon in the listbox. Then again, I don't have a code base that makes a lot of use of this struct, so even just calling the "hwnd" component a load of times, it isn't enough for the IDE to decide that this is the member I am likely to want.
There may be a way to encourage the * icon, but I don't know what it is.
If you set:
VA Options -> Enhanced Listboxes -> Source of C/C++ content: Visual Assist
or set:
IDE tools menu -> Options -> Text Editor -> C/C++ -> Advanced -> Disable Database = True
does this change how this bug shows up? I am expecting that if you disable the IDE intellisense database then the * icon won't show up, so if that is part of the problem then that will "fix" it. |
zen is the art of being at one with the two'ness |
|
|
foxmuldr
Tomato Guru
USA
412 Posts |
Posted - Mar 29 2024 : 10:06:49 AM
|
I can send you an exported .vssettings file that has all of my settings, along with an Export Settings from VAX if that would help? I also don't mind sending you this entire project so you can see it as it's just a small internal test utility.
It works if it's set to source of content Visual Assist:
-- Rick C. Hodgin
|
|
|
feline
Whole Tomato Software
United Kingdom
19020 Posts |
Posted - Apr 02 2024 : 10:35:44 AM
|
So long as there are no concerns with sending in the solution, which would be used purely for testing purposes, that would be ideal, thank you. Also having the settings would be good, since clearly they have at least some impact here.
Please send me the files via email:
[email protected]
including this thread ID or URL in the description, so we can match it up. |
zen is the art of being at one with the two'ness |
|
|
foxmuldr
Tomato Guru
USA
412 Posts |
Posted - Apr 24 2024 : 08:48:08 AM
|
Note: I sent the information to Whole Tomato, but was unable to reproduce the same error later on. I chalk it up to being a fluke. The only thing I can think of is I updated Visual Assist X from a year-old version, and that's when it happened following the update. |
|
|
|
Topic |
|