You are reading a single comment by @allObjects and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@allObjects
@Gordon,
Discussion about scrolling, menu item 'thickness'(line/item-height) of Bangle.js 2 inspired me for a change of the Back menu item: touch on the menu header could be that 'always visible/accessible Back button since we have now touch also being able to detect 'vertical' location, and could present itself as attached image. It is even possible to make it Bangle.js 1 compatible by including the menu header in the selection that are cycled thru...
This lets you even eliminate the Back item. Of course, when entering the menu, the heading would have to be selected to not inadvertently go some-where with 'butt'-touches/button-presses... ;-).
And more: since the back button is on the left side of the the display / menu header and the scroll button is on the right side, touch-behavioral compatibility can be provided for back and (forward) scroll for both Bangle.js 2 AND Bangle.js 1... when enabling touch in menus.
Users will get used to it quickly...
Remains to specify: A) Are button and button 2 in Bangle.js 1 preferred to enter and exit the menu / *settings -item or touch and touch-left/right? - and B) What is then used for flipping/cycling thru values in *settings -item on Bangle.js 2 (if not a full screen or 'pop-up/pop-over' - size reasons - is used for setting values, which also allow easily to have save/exit and cancel on value selection/setting.
See post # in menu time 'thickness' (line/item-height)
1 Attachment