Whole Tomato Software Forums
Whole Tomato Software Forums
Main Site | Profile | Register | Active Topics | Members | Search | FAQ
User name:
Password:
Save Password
Forgot your password?

 All Forums
 Visual Assist
 Technical Support
 VAssistX.NavigateBack always jump to head of line?
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

chjfth
Junior Member

24 Posts

Posted - May 26 2016 :  8:49:18 PM  Show Profile  Reply with Quote
I have VAX 2098(currently latest) installed on my Win7x64 PC. This Win7 has both VS2008 SP1 and VS2015 Update 2 installed (VAX is re-installed after them). But VAssistX.NavigateBack(Alt+Left) exhibits different behavior.

On VS2008, the behavior is correct. For example, line 100 has a call to WinAPI CreateEvent; place caret on CreateEvent, press Alt+G jumps to CreateEvent's declaration, then Alt+Left will jump back to the CreateEvent word on line 100.

On VS2015, Alt+Left jumps back to line 100, but the caret is always placed at head of the line, which is not the expected behavior. Furthermore, every Alt+Left and Alt+Right jumps to head of a line, not to the word position where it was; I don't know what's going wrong.

Edited by - chjfth on May 26 2016 8:50:35 PM

feline
Whole Tomato Software

United Kingdom
15980 Posts

Posted - May 27 2016 :  3:04:36 PM  Show Profile  Reply with Quote
Thank you for the clear description. I am seeing the same thing, but had never noticed the change in behaviour. Taking you back to the column, if possible, would make more sense, so I have put in a bug report about this:

case=97613

Testing, this changed in VS2010, and I know that VS2010 and above are fairly different to VS2005 and VS2008, so this might be a factor.

zen is the art of being at one with the two'ness
Go to Top of Page

chjfth
Junior Member

24 Posts

Posted - Jun 24 2016 :  11:08:54 PM  Show Profile  Reply with Quote
I found a VAX version as old as 10.6.1862 (2011), and it exhibits the same "jump back only to head of line" behavior on VS2010.

It's astonishing that for 5+ years, no one has realized such a change in behavior and got tripped by its inconvenience?

Hope it get fixed soon.
Go to Top of Page

sean
Whole Tomato Software

USA
2640 Posts

Posted - Jun 25 2016 :  12:38:31 AM  Show Profile  Reply with Quote
Yeah, it is odd that no one noticed that it broke when we starting supporting vs2010. It will be fixed in the July release.
Go to Top of Page

sean
Whole Tomato Software

USA
2640 Posts

Posted - Jul 18 2016 :  10:40:53 PM  Show Profile  Reply with Quote
case=97613 is fixed in build 2107.
Go to Top of Page

chjfth
Junior Member

24 Posts

Posted - Aug 01 2016 :  08:06:17 AM  Show Profile  Reply with Quote
Tried 2107, really fixed, works great.
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2019 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000