Event Structure - Access Lock Front Panel option Programatically - VI Scripting

[Sarath_Kumar.T.G]

Hi all,

I am actually having some ten VIs which has event structures with nearly 50 cases each. All those events on creating had the "Lock Front Panel" check box being True. I want to make that Boolean False in all the cases for some UI handling. I thought of writing a Scripting VI to modify the property but I was able to proceed only till the frames in the property node heirarchy and was not able to get the properties which defines a particular event. Does anyone had already tried this or Have a solution ?  The below image is my progress. 

[mikeporter]

You have 10 VIs, each with 50 controls? Forgive me for saying so, but it sounds like you have a lot bigger problems than how to turn off the screen locking.

Why do you need to turn it off on all 500 controls?

Mike...

[Jacobson-ni]

I also couldn't find an answer for you but if you are using scripting to look for an object (Event Structure in this case) it is usually a lot easier to use the Traverse for GObjects VI.

http://zone.ni.com/reference/en-XX/help/371361L-01/glang/tref_traverse_for_references/

I'm not surprised there is no property under frames for this because Frames[ ] is a proprety of Multiframe Structures and most cannot lock the front panel.  I looked through the class browser and found a Event Locks Panel property for a user registered event but nothing equivalent for an event structure.  This may be something that you cannot do but I would be very interested to know if this can be done.

[Sarath_Kumar.T.G]

Thanks for responding back.

My issue is like I load all those VI in a sub panel. I use a simple state machine architecture in all my VI including the top level VI where I load. A particular sequence of operation takes some 1minute plus time and in this time period if some other event is triggered in the front panel its getting locked. Its not allowing to do any operations even in the top level VI. So only I need it to be done for all the events which are handled in all my VI's.

[mikeporter]

The correct solution is to.not have any GUI states that hat take more thanthan about 200ms. If something takes longer than that it should be in a separate vprocess.

Mike...

[paul_cardinale · Accepted solution]

[Sarath_Kumar.T.G]

Thank you so much for giving me the solution.

[mikeporter]

Funny sort of "solution" that doesn't fix the problem.

Mike...

[Sarath_Kumar.T.G]

Mike,

I will move the cases taking more time into seperate process to fix the issue. And whatever I needed to know on scipting, I have got a solutiion.