Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

Feature Requests

Exclude directory option

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

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

[quote][i]Originally posted by illone[/i]
[br]I can set up a scenario.

I have folder named "....\\Native Code\\Third Party\\Shared Projects".  In it I put all Third Party SDK sources in sub folders.  I have one SDK that is a problem (JUCE).  Why its a problem is a different issue; but I explain that at the end.  If I could exclude a folder then I wont have to list each 3rd Party SDK separately and/or keep Juce in a different folder.

The problem with JUCE.
(It defines a bunch of common classes [Array, Line, etc...] in .h / .cpp files.  But it has one entry header file and only this header file is to be included in your code.

It defines the JUCE namespace in this one entry header file that wraps all the #includes to the other files.  When VAssist parses the files in this SDK, it doesn't see any namespaces; so what happens is I have all these common classes defined at global namespace.  I have other classes, in namespaces mind you, that use the same common names; and when a instance is created of, say, Other::Array class, I get intellisense for both Juce's and the Other's Array class.)
[/quote]

Check to include your profile signature.
Check to subscribe to this topic.

T O P I C R E V I E W
dodudo7	Posted - Jul 17 2008 : 5:55:25 PM I think that it can be helpful to have an option to exclude directories from being parsed, the same way as in the Visual Assist Options, there is the C/C++ Directories option to add directories (stable and other). The reason I find this request useful is because there are links between directories, and the same code is now offered from two locations. Thanks!
3 L A T E S T R E P L I E S (Newest First)
feline	Posted - Nov 05 2012 : 3:21:05 PM Unfortunately VA does not have a built in method for excluding directories. Normally the issue we have is getting VA to find and parse more code, not less. Do you have a lot of 3rd party SDK's to list? Are you aware that you can paste several paths at once into VA's C/C++ directorys list, to make entering the paths quicker and easier. For the Juce library, if you type: juce:: is VA listing classes from the juce namespace? I have downloaded Juce to have a look, and what seems to be the main header file, "juce.h", ends with the line: using namespace juce; which may well be a factor in all of this.
illone	Posted - Nov 03 2012 : 5:29:22 PM I can set up a scenario. I have folder named "....\\Native Code\\Third Party\\Shared Projects". In it I put all Third Party SDK sources in sub folders. I have one SDK that is a problem (JUCE). Why its a problem is a different issue; but I explain that at the end. If I could exclude a folder then I wont have to list each 3rd Party SDK separately and/or keep Juce in a different folder. The problem with JUCE. (It defines a bunch of common classes [Array, Line, etc...] in .h / .cpp files. But it has one entry header file and only this header file is to be included in your code. It defines the JUCE namespace in this one entry header file that wraps all the #includes to the other files. When VAssist parses the files in this SDK, it doesn't see any namespaces; so what happens is I have all these common classes defined at global namespace. I have other classes, in namespaces mind you, that use the same common names; and when a instance is created of, say, Other::Array class, I get intellisense for both Juce's and the Other's Array class.)
feline	Posted - Jul 18 2008 : 09:26:58 AM I do not understand these links between directories. What sort of links? Have you considered setting: VA Options -> Projects -> C/C++ Directories -> Platform to custom and then setting just the directories you want VA to know about and parse?

Snitz Forums 2000