Home Community Idea Exchange LabWindows/CVI Ideas Idea

LabWindows/CVI Idea Exchange

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
tstanley

"Custom Copy Directory" improvement idea

Submitted by Active Participant on ‎07-05-2011 12:58 PM 1 Comment (1 New)
Status: Under Consideration
To be clear, the portion of this suggestion that is under consideration is the ability for CVI to automatically consider paths above the project folder to also be relative to the project, as far as the "Custom Copy Directory" directory path is concerned (this behavior already exists for the paths of files in the project, but currently does not exist for other paths in the project, such as "Custom Copy Directory"). However, extending this to the "Specify Executable to Debug" path is not under consideration. The reason is that this option is saved in the workspace, not the project. Paths that are saved in the workspace have a much more restricted notion of relativity to the workspace file than paths in the project to the project file. This is because the workspace file is not really intended to be shared across developers, or even moved to different locations. If the project does need to be moved, it should be fairly easy to create a new workspace or to fix up the previous workspace.

Would it be possible to allow ".." to be used as a "Custom Copy Directory" in the "Target Settings" dialog box (for dynamic link library projects)?  Or in other words, I would like the ability to specify that the Custom Copy Directory should always be one up from the project directory.  That way this functionalty won't break when I rename the directory or move the project between computers where the complete path is not the same.  A similar thing would also be handy in the "Specify Executable to Debug" dialog box.  Thanks.

Labels:
1 Comment
LuisG
NI Employee (retired)
‎07-27-2011 11:53 AM
‎07-27-2011 11:53 AM
Status changed to: Under Consideration
To be clear, the portion of this suggestion that is under consideration is the ability for CVI to automatically consider paths above the project folder to also be relative to the project, as far as the "Custom Copy Directory" directory path is concerned (this behavior already exists for the paths of files in the project, but currently does not exist for other paths in the project, such as "Custom Copy Directory"). However, extending this to the "Specify Executable to Debug" path is not under consideration. The reason is that this option is saved in the workspace, not the project. Paths that are saved in the workspace have a much more restricted notion of relativity to the workspace file than paths in the project to the project file. This is because the workspace file is not really intended to be shared across developers, or even moved to different locations. If the project does need to be moved, it should be fairly easy to create a new workspace or to fix up the previous workspace.
0 Kudos