TS_EDIT now shows up in my menu bar

[mrbean]

I am not sure what I did to cause this, but TS_EDIT now appears instead of Edit in my menu options.  Where is this getting set, and how do I get it to say Edit again?

[Captain_Jack]

Hi mrbean,

This appears to showing the placeholder name that is used by the language .ini files to set the language specific value of menu items. So it appears that you've somehow broken the reference key that is used to replace this with the appropriate string.

I don't know which language file you're application is using for getting these strings from, but the Sequence Editor uses the SequenceEditorStrings.ini file and EDIT = "&Edit" under [SEQEDIT_MENUS] to set the value. It might be that this is missing from the .ini file your application is using to populate the menu headings.

I hope this helps.

[mrbean]

BTW, I am running on a Win10 machine with TS2016 and LV2017.  I see a version of this file in two locations.  One in Program Files (x86), and one in Program Files.  Both are in the National Instruments\TestStand 2016\Components\Language\English, and both have a 4/6/2017 timestamp, implying I haven't changed either accidentally in the last day or so (during all my experimentation).  This brings up a related point.  I'm not sure if this file is allowed to be modified, but if I did, (as was done with ModelStrings.ini), where does TestStand (at runtime) look for these files.  Since there are multiple copies of these files, i'm not sure where i'm supposed to copy MY version of these files (when I install the software on the target).  In the case of ModelStrings.ini, I am placing the file in the C:\Users\Public\Documents\National Instruments\TestStand 2016 (32-bit)\Components\Language\English folder.  This works at my desk PC, but at the target the HMI doesn't find the desired/modified strings when I place that file in the users folder.

[Captain_Jack]

Hi mrbean,

So my understanding of how TestStand handles this is that it first looks in the Public location for components and data files, and if not found there, falls back to the Program Files location. I'm running a much older version of TestStand (2012 and v4.2.1), so things may have changed, but if you're doing a deployment with the of your HMI on the target, I believe you can put your version in the Public Configuration location, and the deployment tool will put it in the proper location on the target. However, be aware that I haven't used the Deployment utility since v2.01f1 - too many issues that we could solve using other simpler deployment mechanisms. So it too may have changed since I last dug into these issues.

I'd suggest trying testing the target .ini files making minor temporary edits to the replacement strings to see which file is effecting what you do see (e.g., rename "Help" to "Help public" in the public .ini file) in your HMI. Then at least you'd know where TestStand is expecting to see these. Also, if you have a CustomStrings.ini file, you could be overriding the EDIT menu option there; as TestStand will use that entry first in place of the normal file it typically uses (Tested in TestStand 2012 Sequence Editor).