LabVIEW

[richard.koo]

I used to be able to type in some value in a LabVIEW numeric control then hit the 'Enter' key to trigger a 'Value Changed' event.  Then at some point in time, this does not work anymore.  I will have to click somewhere else to trigger the value changed event.  The up/down arrow keys still work, but just typing in a number then hit enter does not.  Is it some configuration settings got accidentally changed?  Please help!

[P@Anand]

I see there is no configuration for this. Can you post the vi (I have tried in my machine it works fine) also copy and paste the code into a new vi then run and check it.

[richard.koo]

Thank you for your reply.  I can not post the vi because it is very complicated.  All involved amounts to 45 Mbytes.  I tried it with a simple vi and it works fine, but in my main application, it does not work.

[RavensFan]

45 MB for one VI?  I hope not!

Can you copy and paste that one control and the event structure that handles it to a simpler VI?  Get that simpler VI operational and see if it still has a problem?

[Matthew_Kelton]

I can repeat this behavior by having a boolean control toggle on the Return key, as setup in Key Navigation.  Do you have an OK button or other boolean which does this?  If I check the box to have it set focus on toggle, the number will see the value change event.

[richard.koo]

Thank you for your reply.  Not just 1 vi.  The main application includes some 50+ vi's.  That is just the first level.  When I break out just one numeric control in a debug effort, it works fine.  But the main app still does not work.

[Frabto]

Then you have to look into the main vi/main architecture.Can you post a snapshot of the main  vi 

[richard.koo]

Mathew, thanks for your reply.  I don't exactly follow what your are saying mainly because my problem is with Numeric Control and yours is with Boolean.  Anyway, I did not map any Key Navigation, before and after, thus I don't think that is it.

[richjoh]

sound like you have the event selection to mouse up or mouse down and not value change. can you confirm its value change event. are you using filtered events? Is this LV version 2011

[richard.koo]

nijams, thank you for your reply.  Attached is a screen shot of the main vi, it has grown very convoluted.  Every slider in the front panel triggers several levels of ValueSignaling property chantes and massive mathmatical computations happen and many graphs redraw.  I used to be able to type in a new number, hit Enter to see the change happen.  Now hitting the Enter does not do anything, not even changing the slider.  I have to mouse click outside of the numeric field for the change to happen.