Conversation
checks dom.isactive & allows displayUpdate(force), set true for by default for setValue fixes isactive problems allows drag events, and re-added key up/down
|
The ColorController is affected by this problem as well ; I cloned your branch locally and modified it the same way you did for OptionController, and the problem is fixed.
|
Right! I forgot that one didn't I? PS: I'd classify myself as a mostly-newbie here as well. Here's some resources that got me started: |
An attempt to de-clusterfy .listen,
while still allowing editing of input fields when(isActive)
but allowing setValue to cause updateDisplay, so events like keyboard events will work...
updateDisplay(force): skips active check (note force is false during the .___listening loop)otherwise runs active check and doesnt update if dom.isActive(element)
fixes listen, while allowing editing, allows drag events, and re-added key up/down (which were blocked if checking isActive but not force)
isactive problems: fixes #206, fixes #179
keyboard: fixes #195, (which isactive checks block without upateDisplay(force) option)
possible related, but am confus:
#95: this is true. onChange is fired by setValue, onFInishChange only after slider/mouse event
#212: I don't follow this, though it seems related... a code example might help. I suspect he could updateDisplay(true) after whatever he's doing
withdrawing head from code in 3... 2.... 1....