why does "open vi reference" wait for "mouse up"?

[ckis]

Hi Joe,

thanks for the tip- there seems to be a good source for lv code..

Unfortunately it won't solve my problem because receiving the click is not the problem. No matter what I do as long as the mouse button is pressed the "open vi reference" vi doesn't execute. I'll try the NI support and look for a way to get around using "open vi reference".

Clemens

[JeanPierre]

I can't reproduce your problem with LV7. I've set an event structure to wait for a boolean value change (mechanical action Latch when pressed). On the event occurrence it opens a VI reference (reentrant run). It works as expected. The event executes as soon as the boolean is pressed. Is ther any other differences in your setup?

[shoneill]

Hi Jean-pierre,

I don't think he has the open VI reference IN the event case. From my understanding, it's outside, but is blocked until the event case for the mouse event is finished.

Shane.

[Joe_Guo]

the event structure will catch the mouse down event and process whatever in that case and exit the event structure, it does not wait for mouse up event to occur.

-Joe

[JeanPierre]

CC,

can you repost your example without question marks in the filename please?
We, Windows impaired people, can't read it.

Thanks

[ckis]

Hi everybody,

here's an example vi (LV71) to demostrate the problem I have with "open vi reference". When you press the "OK" button and keep it pressed Labview steps into the event structure but it doesn't completely execute as long as you keep the button pressed. I didn't specifiy a valid file path so that I don't need to post two vi's, but that makes no difference.

Regards Clemens

[chilly_charly]

---

@Jean-Pierre Drolet wrote:
CC,

can you repost your example without question marks in the filename please?
We, Windows impaired people, can't read it.

---

Here it is ! Sorry for the delay, I missed your reply...

CC

[altenbach]

CC,

This seems to work fine if the boolean is set to switch/latch when pressed (LabVIEW 7.1). With these settings, it works fine monitoring either a "value change" or a "mouse down".

This would be the workaround.

[chilly_charly]

Hi Altenbach !
I agree with you, the problem does not appear if the behaviour of the boolean is changed. However, this is not a reply to the question asked by ckis, and I do not find any plausible reason for that !
Not bsure either it could be a work around when you need to detect also a delayed mouse-up...
CC

[altenbach]

---

@chilly charly wrote:
... However, this is not a reply to the question asked by ckis,

---

Well, quoting from the first post in this thread:

...Is there any possibility to get "open vi reference" to execute while the mouse button is still pressed?...

Yes, I agree there seems to be some weird behavior with certain action settings, but it does directly answer the quesion.
(Maybe I am completely missing something obvious, happens all the time.)