How to conditionally disable or otherwise remove EntryPoint2 and Run_Sequence buttons in SimpleUI

[RGTer]

I am trying to muck with the SimpleUI project provided by NI (currently working with the Labview version). I need to conditionally (or permanently) disable the EntryPoint2 and Run_Sequence buttons, based on login permissions. Disabling at the TopLevel VI doesn't "keep" -- when a sequence file using a process model is loaded, these buttons are re-enabled. At what level do I need to disable these?

I sort of successfully deleted them but the UI behavior changed, launching a separate(?) instance of the TestStand application/sequence when a shortcut was used to launch the exe file created with a sequence file passed to it.

Also, the basic SimpleUI is no longer toggling the Login/Logout button on our system. It logs a user out but does not provide a way to log back in (the button text remains "Logout"). Any ideas here?

Thanks!

[herrlin]

I believe you could modify the Display Sequence File callback to check for the desired user group and the enable or disable the button accordingly.  Something like this:

[SercoSteveB]

I don't like messing with the example UIs provided by NI either.  If they contain controls that we don't want, rather than deleting them we move them from the visible part of the UI to somewhere that the user cannot see or access them.

[RayFarmer]

Hi,

Create a User when has Operator rights and when you login as this user both those controls will be disabled.

[RGTer]

Thanks all! The customer has decided this isn't a real big deal so we may just leave things as they are. I will try the ideas to see what works (best). I sure wish I had more time to play, er, uh, experiment with these things.