Event structure hangs UI

[Wiebe@CARYA]

Hi,

In the attached VI, the event structure hangs the UI after when a user
attempted to close the panel. I do not mean the VI doesn't stop. The button
cannot be pressed anymore, and the menus are not handled.

It is offcourse a stupid example, but it still is weird behaviour.

Regards,

Wiebe.



[Attachment Event structure bug.vi, see below]

[Nick_Storton]

Hi,

I think your problem is that you have wired a TRUE to the discard data field this allows you to prevent LabVIEW from processing the event, bypassing the behavior normally triggered by that event.
Try wiring a FALSE I think it now works.

Hope this helps,

Nick

[Wiebe@CARYA]

Hi,

If I'd wire false to the discard, the panel is closed. The hole idea of the
event structure is to prevent this.

If the panel is closed, the event loop should quit. Instead all event are
blocked.

It's not a problem for me, but I think it shouldn't be like this.

Thanks anyway.

Wiebe.


"Nick Storton" wrote in message
news:506500000005000000F4300100-1066448259000@exchange.ni.com...
> Hi,
>
> I think your problem is that you have wired a TRUE to the discard
> data field this allows you to prevent LabVIEW from processing the
> event, bypassing the behavior normally triggered by that event.
> Try wiring a FALSE I think it now works.
>
> Hope this helps,
>
> Nick

[Nick_Storton]

Hi Wiebe,

Ahhh now I see your point. I tried this and interestingly on my machine (Dell P4 laptop, win XP pro, LV7.0) I found the vi worked as you require the first time (the boolean was still operational) but if I select close panel a second time the UI does indeed appear to hang. I think this is something you need to follow through with NI support. Follow this link and select option 2 either phone or e-mail.

http://www.ni.com/support/

Hope this helps,

Nick

[Feroz]

Hi Wiebe,
Thank you for noticing this and bringing it up. I was able to reproduce this strange behavior on my computer. I'm going to file a CAR and pass it on to R&D.

Let me know if there was something in particular that you were trying to do and we can try to find a work around.

Sincerely,
Feroz
National Instruments

[Wiebe@CARYA]

Feroz,

Like Nick mentioned, I've should report this to NI directly. But in my
experiance, this way has better results. It's not a big problem. Using an
event structure like this does hardly have any practical usage. Still, it's
one of the very few bugs left...

Regards,

Wiebe.

"FerozP" wrote in message
news:506500000005000000A3310100-1066448259000@exchange.ni.com...
> Hi Wiebe,
> Thank you for noticing this and bringing it up. I was able to
> reproduce this strange behavior on my computer. I'm going to file a
> CAR and pass it on to R&D.
>
> Let me know if there was something in particular that you were trying
> to do and we can try to find a work around.
>
> Sincerely,
> Feroz
> National Instruments