| Author |
 Topic  |
|
|
Weeblie
New Member
2 Posts |
 Posted - Mar 25 2010 : 12:09:03 PM
|
The file/folder list showing up after typing "#include" feels very buggy compared to Microsoft's default implementation in VS 2010 RC1.
- Forward slashes does not work though one can see the list of files/subfolders "blink" for a fraction of a second before disappearing. For some reasons it does work for the two special folders ".." and ".".
- Sometimes two back-slashes are required in order for the list to show up. This is most common if instead of pressing enter to accept the auto-completion for a folder, you manually type the whole string out, including the back-slash. I.e. to actually type "#include <boost\\".
- Microsoft's default implementation keeps the list open after erasing all characters in the path. VAX closes it. Example: "#include <a" -> "#include<" [list now closes if VAX is active] -> "#include<b".
It would be nice if these behaviors could be fixed or if one could configure VAX not to take the include list over.  |
Nothing is impossible because impossible itself says I M Possible. |
Edited by - Weeblie on Mar 25 2010 12:11:05 PM |
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Mar 25 2010 : 4:49:18 PM
|
I am seeing the same effect here. Thank you for the clear description.
case=41544
There seems to be a random element here.
The listbox when deleting the first letter of the file name, does the listbox reappear after a moment? This is what I am seeing. |
zen is the art of being at one with the two'ness |
 |
|
|
Weeblie
New Member
2 Posts |
Posted - Mar 25 2010 : 5:37:53 PM
|
quote:
Originally posted by feline
The listbox when deleting the first letter of the file name, does the listbox reappear after a moment? This is what I am seeing.
It usually does not. But on a few rare occasions, it does.
---
On closer inspection, I strongly believe that this is because of a conflict between the normal IntelliSense "#include autocompletion" and VAX's own version.
If one looks really carefully, one might see that after typing "#include <", there is actually another file/folder list open for a fraction of a second before the normal one replaces it.
That invisible file/folder list is the same as the one you get if you go from "#include <" -> "#include<<" -> "#include<" -> "#include<<" and has tiny tomatoe-icons behind each icon!
Aha! The normally visible file/folder list seem to be the standard VS file/folder list and not VAX's own list!
So... lets see what happens if we disable this part of IntelliSense (Options -> Text Editor -> C/C++ -> Advanced -> IntelliSense -> "Disable #include Auto Complete").
Both forward and backward slashes work just fine now that VAX and IntelliSense no longer are fighting for the user's attention!
VAX's list is still not working as smoothly as IntelliSense's, but it's at least a step forward:
- (mentioned earlier) VAX's list closes when it reaches 0 characters.
- VAX's list closes after fully typing a file/folder name out but before the ending slash (i.e. closes after typing "#include <boost"). This is troublesome if you want to go "backwards" in the folder hierarchy.
- Once in a while, VAX's list "flickers away" after typing "#include <" (i.e. for all purpose; "doesn't show up").
- (minor) VAX's list doesn't start from the top but from "agents.h" on my system.
- (minor) VAX's list uses forward-slashes in auto-completition. I personally like forward slashes but VS's default (configurable) behavior is to use backward slashes.
---
I hope this will be of any help to you. :) |
Nothing is impossible because impossible itself says I M Possible. |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Mar 25 2010 : 9:46:20 PM
|
Thanks for the detailed feedback. case=41544 (problem with / vs \\) is due to a conflict with the "Filter completions lists..." checkbox in the VA Options dialog (VAssistX | VA Options | Advanced | Suggestions | Filter completion lists). Turning that off fixes the display of the list after typing \\.
VA defaults to using \\ for directories but it will look in the file to see if other include directives use / in which case that will be used. The VA default delimiter is set in the registry but in vs2010 we should use the IDE option. |
|
|
|
sean
Whole Tomato Software
USA
2817 Posts |
Posted - Mar 26 2010 : 6:32:09 PM
|
VA file completion listbox doesn't start from top is case=41565
Problems with backspace and 0 characters is case=41564
VS2010 setting for directory delimiter is case=41553 |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Apr 10 2010 : 9:30:53 PM
|
| case=41544, case=41564, and case=41565 are fixed in build 1819 |
Whole Tomato Software, Inc. |
|
|
|
support
Whole Tomato Software
5566 Posts |
Posted - Jan 24 2011 : 4:11:37 PM
|
| case=41553 is fixed in build 1840 |
Whole Tomato Software, Inc. |
|
|
|
dinaiz
Junior Member
France
13 Posts |
Posted - Dec 12 2011 : 11:28:50 AM
|
quote:
VA defaults to using \\ for directories but it will look in the file to see if other include directives use / in which case that will be used. The VA default delimiter is set in the registry but in vs2010 we should use the IDE option.
Where in the registry should I look, to make the default directory separator '/' instead of '\\' when using VS2008 ? (visual assist X 10.6.1848) |
|
|
|
feline
Whole Tomato Software
United Kingdom
19021 Posts |
Posted - Dec 12 2011 : 2:03:36 PM
|
This FAQ explains the registry setting:
http://docs.wholetomato.com?W337
For VS2008 you want to set:
HKCU \\ Software \\ Whole Tomato \\ Visual Assist X \\ VANet9 \\ DefaultAddIncludeDelimiter = "\\" |
zen is the art of being at one with the two'ness |
|
|
| |
Topic |
|
[1814] Include file/folder list problems.
