This is feature request is a result of the discussion at https://forum.pimatic.org/topic/1789/how-to-use-variableinputdevice. As @Heizelmann stated the problem is the variable is updated on every keypress which in turn leads to trigger dependent actions on variable change. This is undesirable in some use cases and may cause load overload or malfunction of the related actions. Thus an (optional) edit mode should be implemented where editing processes has to be confirmed, e.g., by providing OK, Cancel buttons. Following this, the variable will only be changed if the editing has been confirmed.
A short-term work around solution may be to add a debounce feature where editing changes will be applied deferred, say by 10 seconds. Subsequent changes within the deferral timeout will then be lead to a single variable update. Note beyond, the deferral timeout should be a sliding window, i.e. an editing change should restart the timeout period.