[#FDT-1767] Better syncronization between projects names and launch configurations.

FDT

Better syncronization between projects names and launch configurations.

Created: 07/Jan/11 03:57 PM Updated: 22/Jun/12 06:42 PM

Component/s:

Launching, Refactoring

Affects Version/s:

FDT 4.5.3

Fix Version/s:

FDT

Security Level:

public

Time Tracking:

Not Specified

Environment:

Mac OS X 10.6.5

Review Type:

Review by Product Owner

Description

« Hide

FDT can handle .launch files very nicely, allowing you to avoid numerous reconfigurations for some of your tools for each project. However there's one thing that might be better it seems. As soon you pass a *.launch file to another project it keeps the project name of previous project. Could we pass a var to the name? Like `${currentProject}` or something? It's very minor and yet very handy.

Talking about this node:
<stringAttribute key="PROJECT_NAME" value="Fancy Project"/>

Thanks.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

Dominic Beinenz added a comment - 19/Aug/11 01:58 PM

The same thing is if i RENAME the project, the launches are invisible, because there are two entries in the launch file who don't change

and

Environment: ALL

[ Permalink | « Hide ]

Alan K (Deprecated) added a comment - 19/Aug/11 05:38 PM

Good point guys. There is also the issue surrounding refactoring Project names, as mentioned.

I'm going to update the title to reflect the problem rather than a proposed solution. Using a dynamic project name might be how we do it, but there could be a better way.