Acknowledged
CIQQA-3862

Edge 850: onNextPage/onPreviousPage not fired by buttons

My app uses a CustomMenu and implements the callbacks Menu2InputDelegate.onNextPage and Menu2InputDelegate.onPreviousPage.

These callbacks work as expected on other devices and also in the simulator for the Edge 850. However, on a physical Edge 850 device, they are triggered only by touch gestures and not by button input.

I also have implemented onWrap, but that is not triggered either.

Here is the source code of the input delegate:

https://github.com/openhab/openhab-garmin/blob/main/source/user-interface/sitemap-menu/menu/HomepageMenuDelegate.mc 

the-ninth
Parents
  • in reply to flocsy🤠

    Which example are you referring to?

    Menu2InputDelegate does not provide any alternatives to these functions. On CIQ 5.1 devices such as the Edge 850, onNextPage and onPreviousPage should be triggered by both touch and button input. The only alternative is onWrap, which I have also implemented for devices prior to CIQ 5.1, but it is not triggered either.

    There are no other callbacks that could handle or compete for this events.

Comment
  • in reply to flocsy🤠

    Which example are you referring to?

    Menu2InputDelegate does not provide any alternatives to these functions. On CIQ 5.1 devices such as the Edge 850, onNextPage and onPreviousPage should be triggered by both touch and button input. The only alternative is onWrap, which I have also implemented for devices prior to CIQ 5.1, but it is not triggered either.

    There are no other callbacks that could handle or compete for this events.

Children
  • in reply to the-ninth

    I think I meant the Input sample. And you are right. I was replying from my phone, should've checked it before. However it might still be worth running the Input sample and see if the simulator and the real device behave the same way, because, while it doesn't say anything about it in the documentation of Menu2InputDelegate besides mentioning swipes, it is maybe implemented using the InputDelegate or the BehaviorDelegate. If it turns out that even those are different then it might be pointing to the right direction for Garmin to fix it.