work around for formated numeric control bug

[falkpl]

I am sure that there is posts here but I cant find them. 

I have a numeric with the format %0.1f C to display the units 'C' after the number in my control.  All works except when the same number is entered, the value is forced to zero.  I am sure this was a bug in the past but is still in atleast 2009.  Is there a workaround?

[JackDunaway]

This does not directly answer your question, Paul, but I can't reproduce the bug in 2010 (perhaps it's fixed, or I'm "doing it wrong")

[Darin.K]

This stinking bug has thwarted many an Omega I would put in a control.  I can confirm it still exists in LV10 (perhaps Jack was selecting the entire string in the control and not just the number before re-entering).

Never thought of a workaround, just settled for placing the unit in the caption or a free label while mumbling a few expletives.

[altenbach]

---

@falkpl wrote:

All works except when the same number is entered, the value is forced to zero. 

---

OK, I can reproduce it both in LabVIEW 2009 and 2010. Your description is a bit incomplete, for example it is necessary to enter the exact existing number including the decimal point and the number behind it.

For example if it says 1.0 C and I select the 1.0 (or everything) and enter 1+<enter>, nothing unusual happens, same if I enter 1.+<enter>. However if I select the number (or everything) and enter 1.0+<enter>, the display jumps to 0.0. This is not good!

I'll post it over in the bug thread to make sure we get a CAR for this....

[falkpl]

Sorry for the incomplete discription.  I assumed this is well doccumented but could not find a CAR or doccumentation on it.

I almost released a major bug an my software due to this.  It is unfortunate since using firmated strings look so nice (yes you can even do symbols) and the units move with the numbers.

I hope this is fixed in 2011.

[RavensFan]

This sounds like CAR  235712

See http://forums.ni.com/t5/LabVIEW/BUG-Numeric-control-resets-every-other-entry-with-non-standard/m-p/1...

[JackDunaway]

---

@JackDunaway wrote:

This does not directly answer your question, Paul, but I can't reproduce the bug in 2010 (perhaps it's fixed, or I'm "doing it wrong")

---

OK, I can now confirm in 2010 (the key was typing in the value verbatim, including tenths decimal). This bug manifests itself if even a space follows the format string (e.g., "%0.1f ").

Just toying around - "%0.1f %d" exhibits the bug, but "%0.1f%d" does not. "%d C" also exhibits the bug.

***EDIT - Found a CAR, good, and it appears to be the same bug. ***

[falkpl]

Thanks, I figured there had to be a CAR but couldnt find it with the search tool.  Anyone think of an easy work around?  For now I removed the units from the string fromat, I might overlay it which isnt quite as elegant.