LabVIEW numeric control does not trigger value changed event when Enter key is hit

[ben64]

---

@richard.koo wrote:

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.

---

This doesn't seem to be the case but if you use a system button you don't need to map Key Navigation. The system button toggle by default when the return key is hit. You should check the other controls just to make sure none is set to toggle when the return key is hit.

Ben64

[rawlukn]

Unfortunately this doesn't sound like it will benefit the original poster but I wanted to add my experience for others.

I came across this post because I was observing the exact same symptoms. It turned out a boolean button had the [Enter] key bound to it. I don't recall ever doing this, so I'm not sure how it occured, but I discovered it by looking at the 'Existing Bindings' under 'Key Navigation' for another button. Removing the binding from the guilty control fixed the issue.

[Matthew_Kelton]

Certain Booleans (like the OK/Cancel buttons LabVIEW has on the pallette) already have the key navigation and bindings applied.  You probably dropped one of LabVIEW's OK buttons.  I get burned by this every once in a while, too.

[rawlukn]

---

@Matthew_Kelton wrote:

Certain Booleans (like the OK/Cancel buttons LabVIEW has on the pallette) already have the key navigation and bindings applied.  You probably dropped one of LabVIEW's OK buttons.  I get burned by this every once in a while, too.

---

I am fairly certain I did drop an 'OK' button (which I rarely use) and I was unaware of the built-in bindings. I'm sure I'll forget and get burned again someday, but at least I know why now. Thanks!

[altenbach]

Don't forget to vote for this idea. The automatic key navigation assignment is a huge annoyance!

(I don't mind of certain design templates have assigned key navigation, but it should never apply to anything from the palettes!!!)

[BTC_Admin]

---

@richard.koo wrote:

Crossrulz, thank you for your vi.  It clearly demonstrates the use of KeyDown and KeyDown? which is new to me.  Unfortunately it is not the problem I am having.  I still don't know why my numeric control does not respond to Return or Enter keys any more.

---

You certainly seem to have KeyDown event issue, could it be that you have more than one event structure so you don't see KeyDown in the event structure that you're looking at?  Take a look at the attached vi...

-DP

(Do you have any other numeric control on the same vi that trigger an event while you type in a value?)

[richard.koo]

You may be on to something.  How can I find out which control is bounded to the enter/return key?  Only Boolean controls can do this? If I open the property window of each boolean control, under "Key Navigation->Existing Bindings", what should I see and not see?

Thanks.

[richard.koo]

If I did drop one unknowingly, how do I recover from it?

Thanks.

[altenbach · Accepted solution]

> If I open the property window of each boolean control, under "Key Navigation->Existing Bindings", what should I see and not see?

The table with "existing bindings" should be empty unless you added something. Look for any control that has a <return> key assignemt, then go to the front panel and diagram and find the control with that name. Now open the key navigation property page for that control and set everything to "none". 

Change the circled ring to "none" instead of "return":

 

[richard.koo]

Thank you so much for solving this problem for me.  It has been haunting me for over a year.