@leader21 Strange it does not work for with Chrome 54 on Win 10 64 bit. I even have deactivated all Chrome extension). I’ll now try a plain vanilla setup of Pimatic. Maybe it is some side effect cause by the set of device configurations I have or some plugin causing trouble.
-
How to use VariableInputDevice
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
This problem still exist and apparently also other users are affected.
https://github.com/pimatic/pimatic/issues/1030
EDIT: The following demo does not work for me either on Chrome http://dev.jtsage.com/jQM-Spinbox/ - maybe it is due to the following: http://stackoverflow.com/questions/40257614/jquery-click-event-on-select-element-not-working-as-desired-on-chrome-54
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
@mwittig sry…
i searched the forum but found nothing -
I think I have found the solution. In my case it was caused by adware! See https://github.com/pimatic/pimatic/issues/1030#issuecomment-267278117 for details
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
I use it the first time and observed that the variable is updated on every keypress which in turn leads to trigger dependent action on variable change. This seems not good in my case and I ask if it is possible to change the variable only when leaving focus of the input field.
(A workaround of cause is to use additionally a second variable, a button and a rule but this is not comfortable.) -
Sorry when I ask again. I want to update the variable only when the editing is finished and not on every keypress. Well known editing processes have Ok/Cancel buttons. Wouldn’t it a good idea to integrate this in the Input device? - At least as option?
-
sounds reasonable to me to use a ok/cancel button as option. But I don’t know if that is possible/easy for the coder.
-
Makes sense to me! A possible short-term work around may be to implement a debounce feature. I have filed this as a new feature request - https://forum.pimatic.org/topic/2760/variableinputdevice-add-option-to-update-the-variable-only-when-the-editing-is-finished
"It always takes longer than you expect, even when you take into account Hofstadter's Law.", Hofstadter's Law
-
I use Firefox. +/- buttons do not work for me too.
-
Try this:
https://github.com/pimatic/pimatic/issues/1030mwittig commented on 15 Dec 2016 • edited
No. It is a standard notebook. I think I have found the solution following the advice given in the following forum thread (second last post): https://productforums.google.com/forum/#!topic/youtube/mYBzHWscubo
I used the malware removal tool from malwarebytes.com as suggested and found 8 adware things on my computer (not FlashMall btw). After performing the removal and rebooting the notebook the demo works as expected.It seems to work for the others
-
On my PC and on Android devices everything is OK. ONLY on my notebook it doesn’t work. I checked with Malewarebytes as well as with G Data Internet Security. Everything is clean, but +/- Buttons still don’t work.
-
Status report:
-
My problem with +/- Buttons seems to be soleved. I can not reproduce it again
-
The update-the-variable-only-when-the-editing-is-finished feature is still a feature request see: https://forum.pimatic.org/topic/2760/variableinputdevice-add-option-to-update-the-variable-only-when-the-editing-is-finished
-
A small new problem came up:
If you change a variable may be by rule or from menu variable to a non numeric value, an associated VariableInputDevice of type number will display this value without complain.When trying to update then the variableInputDevice with +/- Buttons an error occurs. -
An optimization idea: VariableInputDevices as well as similar devices needs to be connected to a plain variable. This leads to some redundancy. You can access the value direct from $var and also from $vardevice.input. In most cases it would be enough to have a VariableInputDevice withot a variable in background. If you compare this with other e.g. sensor devices the value is stored internally is enough.
in short: I vote for making the attribute ‘variable’ of VariableInputDevice (and similar devices) optional to use it standalone.
-