App misbehaving on ForeRunner 935. Fine on simulator

You want to do the whole screen in onUndate if you want it to look consistent. You probably have a timer to update the screen and you might try changing that from every second to every 2 and do it all.  There still could be a delay, but that way it's consistent and not a mix.

Couple more minor UX issues:

- When I press the UP and DOWN buttons I expect the screens to slide down and up. (I assume the corresponding touchscreen gestures would be swipe down and swipe up, as swipe right usually means "go back" or "exit")

- On a button-based watch, a series of screens (like data pages or menus) usually "wraps around" (i.e. if you press DOWN on the last page, you're taken to the first page.) I realize that it probably doesn't work this way on a touchscreen watch -- I know that the Menu2 control reflects these differences (it wraps on a button-based watch, but it doesn't wrap on a touchscreen watch)

(Note that if you support the original Vivoactive watch, then the swipe actions for "previous page" / "next page" are actually swipe right / swipe left, and vertical swipes aren't even supported)

My concern was that the run timer then doesn't tick (minor, but I found it annoying).

Is my concern that running an expensive operation every second drains battery a valid one? I'm not sure whether the hardware accounts for lack of work to do by reducing clockspeed or similar. Perhaps updaing every second is fine.

Dresbo said:

My concern was that the run timer then doesn't tick (minor, but I found it annoying).

I'm guessing the user would want to see the run timer tick once per second (imo).

This is what I get now:

[$X/${Y}/17, $X/${Y+1}/17, $X/${Y+2}/17, ${X+1}/${Y}/17, ${X+1}/${Y+1}/17, ${X+1}/${Y+2}/17]
loading tile:https://maps.creativefootprint.co.uk/api/tiles/$X/${Y}/17
loading tile:https://maps.creativefootprint.co.uk/api/tiles/$X/${Y+1}/17
loading tile:https://maps.creativefootprint.co.uk/api/tiles/$X/${Y+2}/17
loading tile:https://maps.creativefootprint.co.uk/api/tiles/${X+1}/${Y}/17
loading tile:https://maps.creativefootprint.co.uk/api/tiles/${X+1}/${Y+1}/17
received response code:-101
Too many requests in the queue
loading tile:https://maps.creativefootprint.co.uk/api/tiles/${X+1}/${Y+2}/17
received response code:-101
Too many requests in the queue
Tile stats: loadedFromStorage=0, savedToStorage=0, loadedFromWeb=81
received response code:-200
Error requesting map:-200
total points in all tiles:0
pointCounts:{}
types To Render:[]
received response code:-200
Error requesting map:-200
received response code:-200
Error requesting map:-200
received response code:-200
Error requesting map:-200
total points in all tiles:0
pointCounts:{}
types To Render:[]
route Id not set. Not loading route

Are you at all surprised I'm not seeing your original problem?

That's a good spot. My code to change the view is:

WatchUi.pushView(dataView,
new DataDelegate(dataView, mSessionManager, MapperApp.DATA_VIEW_1_ID),
WatchUi.SLIDE_LEFT);

but on a button watch I need to change this to SLIDE_DOWN/UP, I guess. 

I'd add a println to make sure the timer is changing as you expect and the screen is updating as you expect.

And if you only update say every 10 seconds, just show the minutes. and not the seconds.  It all depends on how you want to try to save battery.

Why wouldn't you want it to slide down and up on a touchscreen watch?

Are you actually using swipe left and right to switch screens?

Do you have an original Vivoactive or a newer one?

I believe every touchscreen watch except the original Vivoactive uses swipe down and up for the previous / next actions.

How do your watch's native menus and activities work? (Vertical swipes/slides or horizontal swipes/sllides to scroll?)

I suspect this was the problem all the time. I added a toString() to the ID in case that fixed it (but it appears to just fix the printing). I'd actually forgotten that I'd done that until you mentioned it.

So, -200

so I'm doing something stupid I would guess.

The simulator doesn't do this. Could it be a null field in the request. Perhaps the API key (which is now not set)

FlowState said:

I believe every touchscreen watch except the original Vivoactive uses swipe down and up for the previous / next actions.

https://developer.garmin.com/connect-iq/api-docs/Toybox/WatchUi/BehaviorDelegate.html#onNextPage-instance_function

onNextPage() ⇒ Toybox.Lang.Boolean