| T O P I C R E V I E W |
| tom_seddon |
Posted - Dec 07 2007 : 2:07:36 PM
To reproduce, ensure "Commit suggestion with character not valid in symbol" is off.
Then go to a source file, and type "BLAH->", where BLAH is a pointer to a struct of some kind. (If you're in C++, "this->" will do.)
Up pops the member list. Then press "*", and the highlighted suggestion will be committed.
I've seen this happen in a couple of other situations, too, but this is the most egregious one.
Thanks,
--Tom
|
| 5 L A T E S T R E P L I E S (Newest First) |
| support |
Posted - Aug 04 2010 : 5:39:34 PM
"Selections committed with" behavior for member lists is now configurable under VA Options | Advanced | Listboxes. (case=9369), implemented in build 1829. |
| sean |
Posted - Jun 12 2009 : 10:11:49 PM
Build 1727 has support for disabling the default "complete on any character not valid" behavior of C/C++ members lists. It does not have a UI element in the VA Options dialog though.
To disable the default behavior, exit all instances of Visual Studio and add a new registry value:
HKEY_CURRENT_USER\\Software\\Whole Tomato\\Visual Assist X
string value named: MembersExpandOnAny
value: No
Changing the default behavior should only affect the C/C++ experience and is dependent upon the VA listbox "committed with any character not valid in a symbol" option being unchecked (otherwise the MembersExpandOnAny value is ignored).
Please let us know how this works out for you.
|
| feline |
Posted - Mar 20 2009 : 11:36:52 AM
Some changes have been made internally to how settings work for accepting listboxes, but I am not sure if these changes will make it into the next build or not. Also until I get to run some tests on them I am not quite sure how much they will help.
Our basic problem is what settings do we try to use where? The IDE allows you to specify which characters accept a listbox in C#, but it does not offer any settings for C++ or VB. So getting some form of consistent behaviour gets a little tricky. |
| cwdrat |
Posted - Mar 19 2009 : 3:26:40 PM
VA_X.dll file version 10.5.1715.0 built 2009.01.25
Licensed to:
VA X: email@removed (10-user license) Support ends 2009.09.26
DevEnv.exe version 9.0.30729.1
msenv.dll version 9.0.30729.1
Font: Courier New 13(Pixels)
Comctl32.dll version 6.0.2900.5512
Windows XP 5.1 Build 2600 Service Pack 3
2 processors
Platform: Win32
Stable Includes:
C:\\Program Files\\Microsoft DirectX SDK (August 2007)\\Include;
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\include;
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\include;
C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\\include;
C:\\Program Files\\Microsoft SDKs\\Windows\\v6.0A\\include;
Other Includes:
Stable Source Directories:
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfc;
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\mfcm;
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\atlmfc\\src\\atl;
C:\\Program Files\\Microsoft Visual Studio 9.0\\VC\\crt\\src;
I was wondering if there has been any progress on this issue. I'm having a lot of trouble using the .* and ->* operators because of this. If it's a VS issue, then I'm sorry to bring it up again. |
| feline |
Posted - Dec 07 2007 : 2:36:38 PM
When you type dot or arrow after a variable you are actually triggering a member listbox, not a suggestion listbox. If you do this in the IDE without VA installed you will find that the IDE accepts the current item in the listbox when you type any character not valid in a symbol.
The logic here seems to be that the listbox must be correct, so you obviously want to accept the current item.
Currently VA is doing the same thing the IDE does, for consistency. The option "Any character not valid in a symbol" only applies to suggestion listboxes, which only contain VA's best guess, and cannot be assumed to be always correct.
We are looking to change this, and to apply the listbox options to all listboxes.
case=9369 |
