I'm using the latest version of Ignition 8.3, i have a numeric entry on the screen and it works as expected unless I'm entering in 0 for a second time.
For instance, I'm taking some measurements and for tracking purposes i want to track the date and value regardless if its 0 or not.Initially I was using tag change but that wasn't working as if the value didn't change, it wouldn't trigger.
So then I started using an on action performed script on the Numeric Entry Field (NEF), this way regardless of what was entered I could store it into a database. This worked in the designer, but not on my iPhone.
For instance, if I measured 0 today, when I would test the next day and get a zero, when I entered it into the NEF it would not trigger the on action performed. Through testing, I did find if I used 0.0 or 00 it would trigger the on action performed as a work around.
I looked around the forums and didn't see anything similar, is there a better way to get around triggering when the value has been entered, regardless if it has been entered twice? Thanks!
The onActionPerformed on the Numeric Entry Field only seems to trigger when the 'value' variable itself changes, this includes any decimal changes
My typical workaround is to use an onValueChanged script and simply clear the value field afterwards. If you still want the user to be aware of the previous value entered you can set the placeholder with the entered value (it will display greyed out). Not that elegant of a solution but it gets the job done 
If the value is entered manually, I'd add a button and trigger everything with its 'onAction' event.
Added benefit: If the operator makes a mistake when entering the value, it gives him a chance to correct it.
I'm fine with the user not seeing the previous value, I just want to make sure when they enter 0, it gets stored regardless of the last value. I.E. the same value was entered twice.
Maybe an easy work around is to make it a text entry and convert to float for insert. It will always take the entered value that way. Thanks
I can do that too, I originally had it that way but since its on an iPhone I was trying to maximize space and thought it would be easier with just the number entry change. I'll test out again between the button and text entry. Thanks!