NI TestStand Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
kubes_ch

Change the path to localization language directory in TestStand

Status: New

Since our projects involve several developers working in tandem, we manage all project relevant data under SCM (Source Code Management). This way sharing and exchange of data between developers is much easier. To ensure that all developers can access and use the same TestStand Components – especially the language directory – the TestStand configuration directory is also under SCM control.

During the development process if a developer checks out the project folder, for example to „C:\ProjectX“, then the language folder is available under „C:\ProjectX\TestStand\Components\Language“.

 

TestStand ProjectX.jpg

 

In Teststand there is an option to point the configuration directory to a custom directory. To do this, go under the Station Options – Preferences – Configuration Directory,  and change the default path to our custom checkout path.

 

Station Options.png

 

However, even changing this setting, the language files are still get loaded from the default configuration path. In other words, assigning new custom path (which is „C:\ProjectX\TestStand\Components\Language“) seems to have no effect and the older default location (which is „C:\Users\Public\Documents\National Instruments\TestStand“) keeps getting selected instead.

This means, every developer has to copy the ProjectX TestStand folder into the default location manually a SCM update.

 

Suggested solution: make the whole default location directory changeable, to point to a custom directory. Thus during development of different projects, it is much easier to switch between the projects and to have the possibility to check out the code from a SCM to only one directory (and continue working with them).

_______________
Automate LabVIEW builds easy with Jenkins Plugin www.kubes.ch/Jenkins
4 Comments
warren_scott
Active Participant

Language localization is in the TestStand Public directory, not cfg.

you can configure a custom public directory as described here (knowedgebase document 4LJI2Q00):

http://digital.ni.com/public.nsf/allkb/42a0d8b0dcec64fe8625744f007f3a6d

kubes_ch
Member

Hi warren

 

thanks for your post. We know this "workaround" but for us, changing values in registry, isn't a proper solution. Since there is an option in Station Options to change the configure directory, for me and also for the hotline it's incomprehensible why this do not work for the whole config directory.

_______________
Automate LabVIEW builds easy with Jenkins Plugin www.kubes.ch/Jenkins
Elaine_R.
Active Participant

I could see this as part of a larger initiative to make most TS Settings 'workspace / project' dependent, which I know we've discussed for things like station globals for other feature requests on this forum... would something like a project association work for your team? Or is this one of those things where across your company, team A only wants to synch to SCM with the "German" folder, and team B only wants to synch to the "Spanish" folder etc, so maybe it's at a lower level?

warren_scott
Active Participant

Really, there's another issue related to all this, and that is that TS does NOT support unicode.

You can write a sequence file and put a extended character in a step name and it looks great in your system because of your local windows localization settings, but if someone opens it up in aother computer with a different windows language localization, your sequence file looks like crap.  Doesn't end up well for multiple language deployments.