11-08-2006 10:00 AM
11-08-2006 10:04 AM
11-08-2006 10:10 AM
11-08-2006 10:31 AM
11-08-2006 11:40 AM
11-08-2006 12:12 PM
04-17-2007 11:06 AM
Maximus00, like you, I have a huge VI (complex UI with controls/indicators), It is now 2.5 MB in LabView 8.20 (in 6.1, it is about 5mb). I'm looking for the same thing, that is how to disable the Event Structure "locking front panel". Currently, I disable all 50 events for this feature, but this is cumbersome, tedious, and should be a better way. I came across your post and wish LV had a way to programattically disable it, via a property node. The VI I am working is large, and will most likely be used be maintained by multiple developers so it is critical that there is some way to inhibit the "locking front panel", anytime they add or edit an event. It is definitely NOT a good thing to have the VI lock up! By Programmatically disabling all of the event structure's locking front panel, this would protect the VI code from locking up, if a new developer is unfamiliar with the code.
If anyone knows a way to Disable/Lock Front Panel Programmatically let us know!!
-crazycliffy
04-17-2007 01:08 PM - edited 04-17-2007 01:08 PM
Message Edited by Jhoskins on 04-17-2007 02:09 PM
04-17-2007 01:17 PM
Yes the busy cursor is definitely a good idea. I haven't tried messing around with them yet,
But how do you handle cases where let say you want to "Start" continuously acquire data, and have to push a certain button top "Stop" data acquisition? If cursor is set to busy state, then you will be locked out !
04-17-2007 01:32 PM
Its usually a good idea to place your daq and user events in seperate threads for this exact reasom. You want to lock the user events without screwing with your daq timing. This is especially true with complex large interfaces like you describe. I would use the disable property in your situation, this way you can disable all or some of the controls at any given moment.
Paul