Whole Tomato Software Forums

Whole Tomato Software Forums

All Forums

Visual Assist

Feature Requests

Option to compute path from root for includes

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

Screensize:

UserName:

Password:

Format:

Message:

Forum code is on.
Html is off.

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

T O P I C R E V I E W
rryk	Posted - Feb 03 2011 : 10:20:23 AM In our project we refer all included files from the root of include folder which is specified in Project Properties -> Configuration Propertiees -> NMake -> Include Search Path. Therefore all included files should look like that: #include <RTSG/XML3D/Data/XML3DDataEvents.hpp> Visual Assist however when adding references from a refactoring menu for an unknown symbol ("Add include XML3DDataEvent.hpp") adds them as a relative path: #include "../Data/XML3DDataEvents.hpp" which is not desired as source files may travel from one directory to another. Please add an option that allows to use a certain directory as a root for all included files.
7 L A T E S T R E P L I E S (Newest First)
feline	Posted - Feb 17 2012 : 4:19:33 PM Why would you want to use the full path even for files that are in the same directory? Are your files being moved around the directory structure this often?
rryk	Posted - Feb 17 2012 : 09:08:23 AM Thanks. This definitely helps. Can I also force VAX to use full path even for the files that are in the same directory?
accord	Posted - Feb 16 2012 : 5:20:48 PM I think that the following FAQ entry will help you, which has the title "How to stop Add Include using relative paths" which sounds like your solution http://docs.wholetomato.com?W336 What do you think?
rryk	Posted - Feb 16 2012 : 04:12:58 AM Hi, The problem is again there. Actually it is not a bug, but rather a feature request. Relatives paths are also correct, but they are less robust. There should just be an option to prefer including files by absolute path using one of the include dirs as a root rather than relative path from the file that include is added to. P.S. I have created a small test project and tested with it. Apparently for some time it was also including the files using relative path and then changed back to absolute (after several times opening/closing the project). You can find the project here: http://dl.dropbox.com/u/16259710/test_include.7z
feline	Posted - Jul 25 2011 : 11:27:18 AM You might find this registry setting helpful, which you can use to force VA to always use #include <> or #include "" lines for Add Include: http://docs.wholetomato.com?W338
rryk	Posted - Jul 24 2011 : 10:33:10 AM Somehow this bug is gone on its own :).
accord	Posted - Feb 04 2011 : 11:35:46 AM I wasn't able to reproduce the problem here. Did you happen to restart (all instances of) Visual Studio after you set Project Properties/Configuration Properties/NMake/Include Search Path ? You may also need to rebuild symbol databases: VA Options -> Performance -> Rebuild symbol databases If these doesn't help, I will dig deeper to see what might cause the problems for you.

Snitz Forums 2000