LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

event locks front panel

I have been trying to get labview to copy data from a FP table onto the clipboard.  One method I found was to register for the mouse entering table event.  If true then send true value to a case structure that has another event structure that waits for a Ctrl-C, then copy the selected cells.

This works fine except for one problem.  If any key is held down while the mouse cursor enters the table the FP hangs.  Does anyone know why this happens?  I have tried to filter key down events but still can't prevent the program from hanging.

I am currently using v8.0.  Will try on a different machine with 8.5 to see if it makes a difference.

0 Kudos
Message 1 of 8
(3,112 Views)

By default, events lock the front panel until they complete. There is a chekbox on the event configuration panel to turn that off.


BDS wrote:

If true then send true value to a case structure that has another event structure that waits for a Ctrl-C, then copy the selected cells.


This makes little sense. Event structures should not be inside case structures, for example. Can you show us your code?

Message Edited by altenbach on 09-22-2008 12:01 PM
Message 2 of 8
(3,109 Views)
Lock FP is turned off on all cases but still locks up.  The mouse enter case does nothing but writes "mouse enter" to a string indicator.  If the mouse enters the table while a key is down the program hangs. The write to string indicator does not change.  This implies that the key down is somehow masking or modifying the mouse enter event.
0 Kudos
Message 3 of 8
(3,104 Views)

I was mistaken, If I filter and discard the key down then the mouse over works.  But then, it hangs in the second structure when a key is pressed. 

See attached vi.

0 Kudos
Message 4 of 8
(3,095 Views)
It would be so much easier if you could attach a simplified version of your code. Have you done some execution highlighting?
Message 5 of 8
(3,094 Views)

OK, now we see some code. 😉

 

Your program is fundamentally flawed. Event structures are always active, not just when they are in the dataflow.

 

You should use one single event structure and one single while loop. You can keep state information (mouse entered, mouse left) in a shift register. Also, your timeout case is not used, so delete it. If you don't wire a timeout, it is infinite.

Message 6 of 8
(3,091 Views)

Try this cleaned up version (LV8.0). Modify as needed.

 

 

Message 7 of 8
(3,072 Views)

Thanks!

I think I understand event structures much better now.

0 Kudos
Message 8 of 8
(3,057 Views)