Click on unfocused window brings it to front, but is otherwise ignored

[tarheels100]

Whenever any LabVIEW VI (or even a compiled LabVIEW exe) is not "in focus" or is not "active" in Windows, clicking on it brings it into focus but is otherwise ignored.  So if I was clicking on a button for instance, the button press would not register.  This goes for both buttons on the LabVIEW front panel as well as on the window title bar, like minimize and close. 

This was not the case in prior versions of LabVIEW and is very aggravating when using multiple windows at once.  I'm using LabVIEW 2017 on Windows 10, and the problem may be specific to this combination.  Is there any fix for this problem?

[zou]

Used to have an option you set in .ini for this.

Something like "enable click through"?

[tarheels100]

Thanks for the suggestion, but I don't currently see any such option in the labview.ini file.  Do you know the exact name or "key" for this setting?

[zou]

I think it was this one:

dropThroughClicks = TURE

[tarheels100]

I added "dropThroughClicks=True" to my labview.ini file, but it didn't change the behavior. 

For me, this problem only occurs in Windows 10 (confirmed on two different computers).  The issue does not occur in Windows 7.

[Kyle97330]

I have Windows 10 and this problem occurs with me on LabVIEW 2015 but not on LabVIEW 2018.  Those are the only two versions I have so I don't know if it would work on 2017 on my system.  I could swear I read something saying that this was a known issue fixed in 2018 but I can't find it now.

[diabeticdaniel · Accepted solution]

This sounds like CAR 607006.

It should be fixed in LabVIEW 2015 SP1 f10 (or later), LabVIEW 2016 f5 (or later), and LabVIEW 2017 SP1 or later.

[billko]

I actually prefer "one click to focus, one to operate" behavior.  Although inconvenient, it eliminates the accidental button click.  A stray button click can be devastating.

[tarheels100]

---

@Kyle97330 I have Windows 10 and this problem occurs with me on LabVIEW 2015 but not on LabVIEW 2018.

---

I can now confirm that updating to LabVIEW 2018 resolves this issue.  Thanks!