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
 1711: not all Intellisense options showing
 New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic  

trond
Junior Member

11 Posts

Posted - Jan 16 2009 :  1:53:57 PM  Show Profile  Reply with Quote
VS2002 SP1, WinXP SP3, VC++ project. Happens intermittently (no set occurences).
Problem: Sometimes if I open a created project containing a "void main()" line, I see that "void" is red-underlined. Also happens if I type "const", but not with "return", "class", "int". Once this happened just after I change an #include line to point to an inexistent header name.
This problem _always_ coexists with a VAIntellisense problem: if I type "const", I only get a CONST (not "const") option in the list, for int I only get INT, for void VOID etc.

feline
Whole Tomato Software

United Kingdom
18943 Posts

Posted - Jan 16 2009 :  3:26:26 PM  Show Profile  Reply with Quote
After you fix the invalid #include line does this problem go away?
Is this a file specific problem?

Does restarting the IDE help?

These are keywords, VA should not forget about them, or underline them as mistyped symbols. Very strange.

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

trond
Junior Member

11 Posts

Posted - Jan 17 2009 :  03:07:15 AM  Show Profile  Reply with Quote
After fixing the #include it does not go away (and I only _think_ that was the cause).

File specific problem? what does it mean?

Restarting the IDE, (re)building the solution, cleaning, saving, running- none help.

Edited by - trond on Jan 17 2009 03:15:15 AM
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18943 Posts

Posted - Jan 19 2009 :  12:46:46 PM  Show Profile  Reply with Quote
A file specific problem, some problems only show up in specific files. If you open a different code file in your solution VA will behave normally.

When this happens it is normally because something in the "problem" files is confusing our parser, so we just need to find out what is different about the files that show the problem.

Have you any idea what fixes this problem?

Do you work on several different solutions? I am wondering if this problem might effect some solutions, but not other solutions.

I am looking for any form of clue that might help to explain what is going on here, since clearly this is very unhelpful.

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

trond
Junior Member

11 Posts

Posted - Jan 23 2009 :  09:19:33 AM  Show Profile  Reply with Quote
No, working in a different file in the same solution presents the same problem.
Far as I know, it could (and did) happen to a wide range of solutions (from Hello World's to full games)- but sometimes it happens, sometimes not.
Go to Top of Page

feline
Whole Tomato Software

United Kingdom
18943 Posts

Posted - Jan 28 2009 :  2:02:43 PM  Show Profile  Reply with Quote
Can you please try installing VA 1715. I really don't know if this will help, but using the latest version will make it easier to try and find the cause of the problem:

http://www.wholetomato.com/downloads/default.asp

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