Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
 All Forums
 Visual Assist
 Technical Support
 Accepting VAX suggestion eats scope

You must be registered to post a reply.
Click here to register.

Screensize:
UserName:
Password:
Format: BoldItalicizeUnderlineStrikethrough Align leftCenterAlign right Insert horizontal ruleUpload and insert imageInsert hyperlinkInsert email addressInsert codeInsert quoted textInsert listInsert Emoji
   
Message:

Forum code is on.
Html is off.

 
Check to subscribe to this topic.
   

T O P I C    R E V I E W
stefan_reinalter Posted - Sep 24 2021 : 07:50:56 AM
Whenever VAX suggests e.g. an identifier, macro name, etc. it will eat the following scope upon accepting the suggestion with either ENTER or TAB.

Here's a short GIF that shows what's happening:



Notice that when I start typing MACRO in front of Works() and accept it, the result will be "MACROWorks();".
However, when doing the same with Nested::Fails, as soon as I accept MACRO with ENTER, the result will be "MACRO::Fails();", because VAX has eaten the "Nested" scope.

I wouldn't mind it that much if the behaviour was consistent, but it's not, and that throws off muscle memory.
1   L A T E S T    R E P L I E S    (Newest First)
feline Posted - Sep 24 2021 : 10:57:26 AM
Well that's not supposed to happen. This behaviour is controlled by this registry key setting:

https://support.wholetomato.com/default.asp?W640

by default VA should never overwrite a known symbol after the caret. This is working correctly for the function name but failing for the namespace. Using the above setting you can tell VA to never overwrite, which will avoid the random element that is happening here.

We have seen this once or twice before, but its quite rare. I have added this example to the bug report, thank you for this:

case=140801

© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000