Scrolling within Widget with Glances enabled

Hi,

I'm developing a Widget and I would like to have the main page to show a scrollable list. The best way I could find is to create a CustomMenu with CustomMenuItems. However, the simulator throws an exception that the main view has an unexpected type. I assume it has to be a WatchUi.View object and cannot be a CustomMenu object. I can understand this limitation for the case when widget glances are disabled because in this case, the UP/DOWN buttons bring to the previous/next widget, instead of navigating inside the CustomMenu.

I would like to have similar behavior to the built-in Notifications widget. If widget glances are disabled, then the main view of the widget shows a preview of the notification list, and the user has to press START to get the scrollable list of notification items. However, if widget glances are enabled, the user is immediately brought to the view with a scrollable list of notification items. Could you help me on how to implement a similar widget? Thank you in advance!

  • Has anybody managed to solve it?

  • I am stuck on this too... Have you been able to figure something out? Tx

  • What target device are you trying this on?  Not all allow this.

  • I'm developing a Widget and I would like to have the main page to show a scrollable list. The best way I could find is to create a CustomMenu with CustomMenuItems. However, the simulator throws an exception that the main view has an unexpected type. I assume it has to be a WatchUi.View object and cannot be a CustomMenu object. I can understand this limitation for the case when widget glances are disabled because in this case, the UP/DOWN buttons bring to the previous/next widget, instead of navigating inside the CustomMenu.

    (I realize that I'm quoting a 2-year old post)

    Just my 2 cents, but I'm disappointed with the fact that the main view of a widget in glance mode has similar restrictions to the main view of a widget in non-glance mode (e.g. you can't pop the main view), because it means that in some esoteric use cases, your UI is actually more complicated when glance mode is enabled.

    In other words, even though the glance view is supposed to take the place of the full widget's main view, the full widget's main view still has certain restrictions which only make sense in non-glance mode (IMO), which means sometimes you have to have an extra front page for your glance-enabled widget, with less functionality then you'd like.

    (This use case seems to be another example).

    I am stuck on this too... Have you been able to figure something out? Tx

    Personally, I get around this kind of situation by having an extra "placeholder landing page" for my main view in glance mode (which would be similar to the main view in non-glance mode).

    - When the user goes from glance mode to the "full widget" by press START, I immediately push the *real* main view in onUpdate() so the user doesn't see the placeholder view. Now I can do whatever I want with the "real" main view (which is actually the 2nd view of my full widget.)

    - Unfortunately, when the user exits the real main view, they will finally see the placeholder page, and will be forced to press BACK again to fully exit the widget. I can't think of a way around this, except to pop the main view (which you shouldn't do because it causes the app to crash.) I wish you could pop the main view in glance mode, but I realize this is never going to happen.

    I realize this isn't the greatest UX, but it's the best compromise I could come up with. In my case, I need to be able to override the BACK button, so I'm not able to use my real main view as the widget's main view.

  • I'm on a Fenix 6S Pro. All the native widgets use Up/Down button on their main view to scroll through graphs & data. I hoped I would be able to keep the same user experience.

    I guess I will do the same as @FlowState suggested.

    Thanks everyone.

    EDIT: apparently you CAN use Up/Down from main view when Glance is enabled (https://developer.garmin.com/connect-iq/connect-iq-basics/app-types/). Still need to figure out how to code the Menu2 basically from scratch...

  • Still need to figure out how to code the Menu2 basically from scratch...

    Just for the benefit of anyone else reading this thread:

    forums.garmin.com/.../1314098