Huge widget problems with BehaviorInput

Hi,

I wanted to transfer a widget to the new vivoactive 3. Up to now I used InputDelegate to handle up/down withing the widget which worked fine. I have rewrote the code to use BehaviorDelegate and used instead of onKey function the onNextPage() and the onPreviousPage() functions. This did also worked in the simulator for the vivo 3 as well as for the FR935. But as soon as I transferred it to my physical FR935 a up/down within the widget did not change my widget page but instead my widget was unloaded and the next/previos installed widget was shown.

Any ideas why the watch behaves in this way also the simulator worked well?

gasteropod over 8 years ago

When you are on the initial view you cannot use up and down as this will scroll through the widgets. But once you push another view you should be able to do this. I'd expect the simulator and watch to behave the same though. In the simulator, when using up and down from the initial view I'd expect the widget to exit and show the blue triangle.

Are you talking about from the initial view or are you seeing this behaviour from a secondary pushed view?

Maybe you can give the SDK version you are using too.

topcaser over 8 years ago

Hi,

I see this behavior from a secondary pushed view. As I said before, it worked pretty well with the inputDelegate using the onKey(evt) method. I am currently using SDK version 2.3.5.

Thanks for supporting

peterdedecker over 8 years ago

I suppose you're properly returning true to set the event as handled?
If so it sounds as you found a bug, create a simple reproduction project and post it in the bug forum.

Former Member over 8 years ago

It's the return make sure you're calling it, I had the same problem yesterday and that was the fix.