Input visual element has a frustrating delay

[AlexandreSajus]

The input visual element will register the inputted text at a specific time delay (defined by the property change_delay). When this register happens, the app will have a quick lag that will cause typed text not to be registered. This is very frustrating: The user is typing something, stops for half a second, and then continues typing, and some of his new characters are missing.

You can test this issue on TalkToTaipy or TaipyGPT. Just type at different speeds while taking quick pauses; some characters won't be registered at some point, which will be frustrating. You can also try it on mobile; the change_delay seems to change between local, Cloud, and Mobile.

Expected change The text should only be registered regularly if the user defines an on_change function. In my two use cases, I only need the user's text when he presses "Enter" (on_action). I do not need it registered regularly, so I did not define on_change.

[AlexandreSajus]

We have been getting many complaints on this, switching priority to critical. Also there might be the same issue on the slider visual element

[FlorianJacta]

For the slider, you have the continuous property to not call the on_change function every time the variable is updated.

[AlexandreSajus]

Sometimes, even with continuous disabled, the app does not have enough resources to keep up and will lag the slider. Maybe that's another issue

[FredLL-Avaiga]

when changeDelay = -1 & Enter in ActionKeys (or no ActionKeys) => the input value will be updated only on Enter

[FlorianJacta]

What is the reason to also have an on_action? Will the value still go to the on_change callback each time if there is an on_action and no on_action?

[FredLL-Avaiga]

What is the reason to also have an on_action? Will the value still go to the on_change callback each time if there is an on_action and no on_action?

Fixed the spec