LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Event Structure for inactive window

Hello, I am wondering if there is an easy way make the user events more consistent when the front panel of a VI is not the active window (in Windows). I notice that when a front panel is running but not the active widow I still get button animations and mouse enter and exist events but I don't get button press or mouse down events unless I first click on the window to make it active. I would really like to get the button press and mouse down events even if the window is inactive. If that is not possible, I would like to disable the animations if the window is inactive. I have provided a VI that demonstrates this behavior. 

 

Thanks for looking

______________________________________________________________
Have a pleasant day and be sure to learn Python for success and prosperity.
0 Kudos
Message 1 of 22
(398 Views)

When an app that is not the active window receives mouse click events, that is called 'click-through'. I believe that it is an OS setting/characteristic.

Message 2 of 22
(383 Views)

@paul_a_cardinale wrote:

When an app that is not the active window receives mouse click events, that is called 'click-through'. I believe that it is an OS setting/characteristic.


Yes, this is expected - and desired - behavior.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 3 of 22
(357 Views)

@billko wrote:

@paul_a_cardinale wrote:

When an app that is not the active window receives mouse click events, that is called 'click-through'. I believe that it is an OS setting/characteristic.


Yes, this is expected - and desired - behavior.


Which do you mean?

  • It's desired that it be an OS setting
  • It's desired that there should be click-through
  • It's desired that there should not be click-through
0 Kudos
Message 4 of 22
(348 Views)

@paul_a_cardinale wrote:

@billko wrote:

@paul_a_cardinale wrote:

When an app that is not the active window receives mouse click events, that is called 'click-through'. I believe that it is an OS setting/characteristic.


Yes, this is expected - and desired - behavior.


Which do you mean?

  • It's desired that it be an OS setting
  • It's desired that there should be click-through
  • It's desired that there should not be click-through

As an end user of an application, I think the expected behavior is that if I'm hovering over a button and the button is animating, I expect that clicking the button would do the thing linked to the button ... I don't care if the window is active or not. 

______________________________________________________________
Have a pleasant day and be sure to learn Python for success and prosperity.
0 Kudos
Message 5 of 22
(327 Views)

Inactive window does not get mouse click message is the Windows default behavior.

LabVIEW buttons are not Windows objects.

Why animation works?  An NI mistake.  Should not overwrite Windows default behavior.

 

George Zou
0 Kudos
Message 6 of 22
(320 Views)

I think this works

 

snip.png

 

I don't know why the Event Structure is blank, should be Pane:MouseEnter

0 Kudos
Message 7 of 22
(298 Views)

@Jay14159265 wrote:

@paul_a_cardinale wrote:

@billko wrote:

@paul_a_cardinale wrote:

When an app that is not the active window receives mouse click events, that is called 'click-through'. I believe that it is an OS setting/characteristic.


Yes, this is expected - and desired - behavior.


Which do you mean?

  • It's desired that it be an OS setting
  • It's desired that there should be click-through
  • It's desired that there should not be click-through

As an end user of an application, I think the expected behavior is that if I'm hovering over a button and the button is animating, I expect that clicking the button would do the thing linked to the button ... I don't care if the window is active or not. 


It's desired because if a pop-up shows up in front of the app that has focus, the first click on a button on the pop-up will set the focus, not click the button.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 8 of 22
(279 Views)

@billko wrote:

@Jay14159265 wrote:

@paul_a_cardinale wrote:

@billko wrote:

@paul_a_cardinale wrote:

When an app that is not the active window receives mouse click events, that is called 'click-through'. I believe that it is an OS setting/characteristic.


Yes, this is expected - and desired - behavior.


Which do you mean?

  • It's desired that it be an OS setting
  • It's desired that there should be click-through
  • It's desired that there should not be click-through

As an end user of an application, I think the expected behavior is that if I'm hovering over a button and the button is animating, I expect that clicking the button would do the thing linked to the button ... I don't care if the window is active or not. 


It's desired because if a pop-up shows up in front of the app that has focus, the first click on a button on the pop-up will set the focus, not click the button.


Beyond that, I want the following OS setting:

DontMoveStuffAroundUnderTheMousePointer = TRUE.

Message 9 of 22
(275 Views)

@mcduff wrote:

 

snip.png

 

I don't know why the Event Structure is blank, should be Pane:MouseEnter


Snippets do not maintain static links (UI events, locals, static refs, linked properties, linked methods) to front panel elements that cannot be included in the snippet itself, such as panes and splitters.

Message 10 of 22
(252 Views)