Application pauses during user interaction

[pincpanter]

Hi all,

I have a LV app essentially composed of three parts:

- one main free-running loop that takes care of the app logic and the fp indicators

- one loop containing an event structure for extra dialog windows

- one vi running in the background performing data acquisition from a serial device

The application is "paused", that is fp indicators are no more updated, in two cases:

- when the user opens a control shortcut menu

- when the user opens the selection list of a menu ring (this is the only menu ring on the main front panel)

The data acquisition vi is not paused, as expected (it is not executed in the UI thread). 

The application continues to run when the menu or list disappear.

I tried to reproduce this behaviour in a small vi that I could post, but with no luck.

The first condition can be obviously neutralized by inhibiting shortcut menus from being displayed, but I have no solution for the second condition.

Thank you in advance for any suggestion.

Message Edited by pincpanter on 03-09-2009 03:39 PM

[LiciaP]

Hi Paolo,

it's quite difficult to understand what is causing the behaviour you are observing... I tried to reproduce with a menu ring, with no success.

Maybe a few more details on your application could be useful: the front panel indicators are connected to the acquisition loop? The menu ring or the controls are related to events of the event structure?

To avoid using the ring, you could use an array of strings: the effect is not the same, but it could be a workaround...

Bye!

Licia

[pincpanter · Accepted solution]

Ciao Licia,

finally I could work on the problem and narrow down the cause: the application locks on a Open VI Reference node whenever the menu ring is showing its selection list.

That operation was not really needed and so I could drop this part of the code. Remark that LV locks whether the dynamically called vi exists or not. I'm attaching a simple example.

I guess if this is expected behaviour and what would happen with more recent versions.

Bye