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
 Autocompletion bug in #include
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

leto58
Junior Member

17 Posts

Posted - Sep 24 2007 :  09:21:10 AM  Show Profile  Reply with Quote
Hi,

I need to include 2 header files "..\\dir\\abc.h" and "..\\dir\\def.h".

if I type #include "..\\<cursor>" and press ctrl+space, no problem, I get a list of available subdirectories, and so forth until the end of the path.

but since I am lazy, once I have written #include "..\\dir\\abc.h" the previous way (with working autocompletion), I just copy this line and try and edit it to replace "abc" with "def".
- I doubleclick on "abc" to get the whole word selected
- I type "d"
- I press ctrl+space and I get the box where I can pick "def.h", as expected, BUT the whole path is selected in the same time. When I select "def.h" in the list, it replaces the whole path and I get #include "abc.h" instead of #include "..\\dir\\abc.h".

I expect that when I press ctrl+space, VA does not extends the selection to the beginning of the path, but only from the first char after the last "\\", since it is the part of the path the autocompletion box is proposing.


Regards,
Leto

feline
Whole Tomato Software

United Kingdom
19014 Posts

Posted - Sep 24 2007 :  11:33:58 AM  Show Profile  Reply with Quote
Which IDE and version of VA are you using?

I am not seeing any such problem in VS2005 with VA 1561. When I press CTRL-SPACE the file name is selected, "d.h" in your example, leaving the directory information alone.

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

leto58
Junior Member

17 Posts

Posted - Sep 24 2007 :  4:27:30 PM  Show Profile  Reply with Quote
I am using VS2005 SP1.
I downloaded 1561 this morning, and checked if this problem had not been fixed in this version before posting.

But I just found out that if I wrote my paths with "/" rather than "\\", it worked perfectly well. (I did not even remember it was possible to write #include paths this way :-) )

Anyway, I'd rather like VA to work with both "\\" and "/" than changing the way I write paths...

Regards,
Leto
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
19014 Posts

Posted - Sep 25 2007 :  11:00:42 AM  Show Profile  Reply with Quote
I am seeing the same problem now I am using the correct slash. I always use / in my #include statements, a habit I picked up under UNIX

case=9042

zen is the art of being at one with the two'ness
Go to Top of Page
  Previous Topic Topic Next Topic  
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
© 2023 Whole Tomato Software, LLC Go To Top Of Page
Snitz Forums 2000