Hi,
I would like to get the OnChange event trigger for the following input widget too:
Number widget
In my use cases the change of a value (input widget) via up/down-control effects other fields (calculation results)
So it would be helpful to get this trigger also as it exists for the single select widget
Is this on your timeline/radar?
Regards Chris
Hi @ChrisF,
Thanks for the feedback. We don’t currently have implementing an “OnChange” trigger for the Number Input widget. This is an interesting idea, and I understand why it would be helpful for your use case.
Let me suggest a couple options that might help you in this situation.
Implement “Up” and “Down” buttons to control the value. This will allow you to fire a trigger each time one of the buttons is pressed
Checkout the Change Detector Widget in the Tulip Library. This might have the capabilities you’re looking for to help with your current use case.
Adam
The single select widget fires the trigger when changing the value, the number widget should do so when changing the value via the integrated up/down controls.
Additional Up/Down buttons are irritating because they are there twice.
And yes, the Change detector widget is the workaround I’m using.
But the functionality should be consistent over all widgets.
Regards Chris
I agree with @ChrisF.
I was deploying an app the other day. The app builder had put a trigger with some actions on a text input field and didn’t understand why the actions weren’t executed despite changing the value. Having to hit the Enter key is definitely not a reflex the users had in the shop floor from what we could see. We found a workaround though.
Another time, I was building an app that needed to show computed numbers depending on a weight number input. I used the change detector custom widget which greatly improved user experience. Having to click buttons or change steps is less user-friendly.
It would be nice to have this “on change” behavior on all input types.