06-29-2018 08:39 AM
Hi
I would like to remove the login option from File menu at runtime. Essentially we are using the seq editor to run test and have found that when executing code the Login button is still active and can be used. I am looking for the ability to programmatically modify the Teststand menus. Currently using Teststand 2016. Thanks
07-02-2018 04:51 AM - edited 07-02-2018 04:55 AM
"have found that when executing code the Login button is still active"
What do you mean by that?
You Log yourself in at the beginning but when you run the sequence file it pops out again?
Edit: In runtime you can modify a lot Teststand configuration. You can modfiy some Configuration related to the Login with this -Action- .
07-11-2018 10:57 AM
Thanks for the response. What I mean by "have found that when executing code the Login button is still active" is not that the login screen stays open or pops up on its own. It is actually that when you are running a Teststand seq at any time while it is running you can go under the File menu in Teststand and select to Login. This can change who is logged in in the middle of testing and we have steps that have preconditions based on the permissions of who is logged in. I want to remove the login option at runtime to remove this potential issue then put it back once the sequence stops.
You can create a simple Teststand seq with just a popup at see the same feature when the test stops at the popup.
07-12-2018
02:40 AM
- last edited on
12-09-2024
04:08 PM
by
Content Cleaner
Ok I get it. One way to solve this are the "Operator Interfaces" https://www.ni.com/en/support/documentation/supplemental/14/working-with-the-teststand-simple-user-i... you can customize them as much as you want.
I'm also a beginner in Teststand but I don't think you can modify the thing mention in the normal Teststand Interface.
Regards.
07-18-2018 04:29 AM
I've never worked with that special callback but with others. Usually modifying them is pretty straightforward.
Search the TestStand help for "Modifying Front-End Callbacks" and "Managing Users" (both in "Fundamentals") the info there should give you a starting point.