Interface locked

[Blanky]

Hi,

I know this is a little bit (not to say very) difficult to solve, but i have the problem that in a labview (8.5) program i am writing the interface is locked while doing a certain operation, that means i cant click anything, including the cancel button, and thats my problem.

I was not able to reproduce this on a smaller scale, i have attached the Try so you can see how the program is build up.

Does someone has any idea what it could be ? I know this is difficult because i dont have more information, but some ideas would be really nice.

Thank you

[smercurio_fc]

Aside from the fact that none of your local variables are required (for the buttons "Latch When Released" mechanical action), what is this program supposed to do, and where does it get "locked"?

[Blanky]

I used the local variables because i do it in the "big" program too that way, i know they would not be needed here. The program should wait for a specified time and show this time. When it is in this part, it "locks".

[yenknip]

If your 'big' application is using variables in a similar way, then I would suggest rethinking your architecture.
Your stop button is misleading in that it does not stop the application, it changes the state to 'wait'
The only way to stop the application is to hit the abort button
I'm not entirely sure why you are using a timed loop structure

From your posts, I think what you mean your problem to be is after clicking (and holding until it is read) the start button, the string indicator should count the seconds as they pass?
This display is going to jump in intervals of 6 seconds because you have a wait 6000ms function block in the stabilise state.

[Blanky]

Ok, it was a bit misleading.

That it jumps in 6 second intervals is ok, its just as information. And the stop button shall only stop the current process (stabilizing) and return the application to the wait state.

The Problem is, that during the process it "locks" th whole interface, so i cant use any text boxes, click any drop down menus, i cant even use the x button from the window, and, what the main problem is, i cant click the stop button.

[Britoa]

Ok, I don't have 8.5 installed to view the VI, but your process section that you mention, is that a subVI?  If it is, are you sure that it is exiting properly?  If another event case isn't completed, it will tend to lock the front panel until it completes.  (just a thought)

[Blanky]

No its no SubVI, its directly in the main program. There are other event cases, but they all have a timeout of 100ms, so they should be timed out definetly at the time my problem is appearing.

[yenknip]

I don't get any problems with Front Panel inactivity in the example you posted, only that front panel widgets are not interrogated until the next loop iteration. The Window x button closes the window as it should, Maybe the problem is somewhere else in your larger program?

[Blanky]

Yes, i said already that i couldnt reproduce the problem in the smaller example. I just posted it that you have an idea of the architecture im using.

Do you have any ideas what it could be other than the things in this example ?

[Blanky]

Ok, i was able to reproduce the problem now in the smaller program. I used an event structure to start it. Seeing this now, i may be able to bypass the problem, nevertheless it would interest me why it doesnt work this way, or maybe if im the only one where it doesnt works. Attached is the new version of the test application.