-
@Gordon this is because the
if
check is happening inonchange
, which is triggering even when the value isn't submitted.Edit: I was looking at
master
and not theRELEASE_2V12
tag for this analysis, which might still be true formaster
, but does not apply to this discussion.RELEASE_2V12
analysis appears below.master
If I'm reading it correctly it looks like there is a discrepency in E_showMenu_Q3.js where if the list is short it will use
Bangle.setUI
directly with updown and it will only callitem.onchange
when an item in the list is selected (dir
is not set in theBangle.setUI
cb
), butE.showScroller
fires select (and thereforeE.showMenu
's item.onchange) every time the scroll position is updated.RELEASE_2V12
E_showMenu_Q3.js
will triggeronchange
every time the menu calls move.If that analysis is correct it would be nice to rectify it and have two functions, one for as the item scrolls and one for as the item is saved. For
RELEASE_2V12
it would be straightforward to leaveonchange
where it is called withinE_showMenu_Q3
'smove
and add something likeonsave
to the else where the selection is made, but for the code inmaster
it's not as straightforward.
I didn't try that no :)). My problem is that I don't even need to select the content of a box to trigger that reaction, if I just scroll it (without selecting it) it cleans everything else. It makes the setting of the boxes very difficult.