Apologies if this has been asked before, but I couldn’t find anything in the documentation or the existing forum questions.
I would like to know how I should code for devices with five buttons (LIGHT, UP, DOWN, BACK, ENTER, etc.) when interacting with Widgets during an Activity (Running, Walking, etc.). Specifically with regards to navigating between different Views in a Widget (like pagination).
I own a VA4 so I know an approach for touchscreen-based devices (i.e. allow user to tap on left/right side of the screen).
From browsing the forums I found a post about pushing a secondary view for devices that do not have Glance Views (or have them disabled) in order to allow the user to press UP and DOWN buttons in the Widget itself. I have this set up and working, however I’m concerned about the UX of this behavior. The Widget I am coding automatically pushes the second view in order to allow pagination between the different screens to work right away without having the user push a button to activate said pagination. They can exist the pagination via the back button, and then resume normal UP DOWN scrolling through the Widget Loop.
The user manuals, and posts in this forum, seem to indicate that pressing the ENTER button (top right button when looking at the watch) will always take the user back to the Activity, regardless of watch make/model. I also thought about using the LIGHT button but this doesn’t seem to be available for non-native widgets to “listen” for in onKey. I mean, the button exists in the API documentation, but you can’t click the button in the simulator, and other posts in this forum seem to indicate that this isn’t possible for CIQ widgets.
So, is there a button that I can “listen” for in onKey() that will allow me to know, without a doubt, that the user wishes to “enter” the widget and begin paging through the various screens via the UP and DOWN buttons?
Thanks in advance!
