LabVIEW user interface event structure "priority"

[Terry_ALE]

Do Pane events get processed first and then control events?

I have a VI that checks a value change of button that is latched and it also checks for the mouse down event on the Pane.  I noticed that the Pane event gets processed and then the value change of the button.  This is not too critical at this point for my project but was curious if this is on purpose.

Attached is a VI that does this.

[ben64]

That seems logical since the control is contained in the pane.

Ben64

[GerdW]

Hi Terry,

I have a VI that checks a value change of button that is latched and it also checks for the mouse down event on the Pane.

Your button is set to "latch when released" (aka latch on mouse-up).

So it seems very clear to me that you first get the mouse-down event followed by your value change event, which is the same as a mouse-up event in this very case…

[ben64]

---

@GerdW wrote:

Hi Terry,

I have a VI that checks a value change of button that is latched and it also checks for the mouse down event on the Pane.

Your button is set to "latch when released" (aka latch on mouse-up).

So it seems very clear to me that you first get the mouse-down event followed by your value change event, which is the same as a mouse-up event in this very case…

---

Good catch. I built a simple vi with a boolean mouse down event and pane mouse down event. The pane mouse down execute first when the boolean switch is pressed.

Ben64

[Terry_ALE]

No matter what the mode of the boolean mechanical action, the mouse down pane always runs before the value change of the control.

See attached VI where I output the event type to an array so we can see what actually ran and in what order.

I am looking for deeper feedback on the order of how things run in LabVIEW behind the scenes.

[Hooovahh]

When debugging what event occures in what order, I usually find the Event Inspector Window helpful.  It basically tracks the queue that LabVIEW uses and shows the order that events are generated and handled.

http://zone.ni.com/reference/en-XX/help/371361K-01/lvdialog/event_inspectorwindow/

https://decibel.ni.com/content/blogs/Sixclear/2013/11/04/vi-high-51-event-inspector-window-flushing-...