Edge 1000 menu and back buttons not great

Former Member over 9 years ago

Hi,
I was trying to update my widget for Connect iQ 1.2.x and tried to allow the Edge 1000. My widget has menus that are accessed through key 13 on a watch or the onMenu event in the vivoactive. Annoyingly the edge has two buttons which are 18 and 19 and does it not support onMenu, and why have you numbered the buttons differently to watches? This can be coded around, but it is a pain.

What doesn't seem to be easy though is exiting a menu. The watches and the VA all seem to provide a back button in a MenuInputDelegate, but not the Edge.

Any thoughts on how to get out of a menu? Do I really have to code for it? Or does the device behave differently to the simulator?

R.

jim_m_58 over 9 years ago

Is there a reason you're building for the Edge? It's a different "model" for user input, I've heard.

The best solution right now is probably to just un-mark the Edge as a target, and test the others.....

Former Member over 9 years ago

Because it is there

I decided to try it because it is there, more of a PoC really. I'd hope that some apps could be made to work on any device without significant rewriting. Judging by the look of it in the simulator, you might expect it to behave more like the VivoActive, with two buttons and a touch screen.

I thought that the Garmin developed Menu delegates would behave sensibly though and have a way out of them using a Back button or swipe, but I can't get the simulator to play ball..

I raised this to feed it back to Garmin, as I think they read this forum.

R.

Is there a reason you're building for the Edge? It's a different "model" for user input, I've heard.

The best solution right now is probably to just un-mark the Edge as a target, and test the others.....

travis.vitek over 9 years ago

They know about it already. Right now they're expecting planning support for data fields first, then widgets and apps.

Travis