Strange error with Event Structure!

[Marc Brandes]

Hi,

I have an event structure with 5 cases: 3 cases are toggled by boolean controls with latching mechanical action, while the other 2 are toggled by boolean switches. The strange thing is, that when I toggle one of the 3 latches (let's call it "latch one"), the allocated event case is executed, but after this I can't use any front-panel object anymore. The other events are working as they should. Only when I use "latch one", the front-panel is blocked.
The sub-VIs and functions I use are pretty simple. I don't acces the front-panel in any VI. So I'm realy wondering, what's going on.
Has anyone any idea?

Thanks for your help in advance.

[DEM@ORNL]

Are you reading the latched booleans in the event loop? If not, they
remain activated and thus cannot trigger and further "change."

David McMillan
Oak Ridge National Laboratory

Marc Brandes wrote:

> Hi,
>
> I have an event structure with 5 cases: 3 cases are toggled by boolean
> controls with latching mechanical action, while the other 2 are
> toggled by boolean switches. The strange thing is, that when I toggle
> one of the 3 latches (let's call it "latch one"), the allocated event
> case is executed, but after this I can't use any front-panel object
> anymore. The other events are working as they should. Only when I use
> "latch one", the front-panel is blocked.
> The sub-VIs and functions I use are pretty simple. I don't acces the
> front-panel in any VI. So I
'm realy wondering, what's going on.
> Has anyone any idea?
>
> Thanks for your help in advance.

[Jeremy Braden]

I am assuming that you have an event structure inside of a loop. Put the terminal of your button inside the loop. This will allow it to pop up. Remember the front buttons pop back only after they are read.

Jeremy

[Marc Brandes]

Hi,
I already answered DEM@ORNL posting, but somehow my answer didn't appear. I deleted the bugging event case ("latch one") and the corresponding control. After reprogramming the structure, everything works as it should. So I think there was some kind of internal bug in LabVIEW I produced in a "mysterious" way.
Thanks for your posting!