Need Help Debugging Actual Device Rendering of Widget?

Former Member
Former Member
I have the following widget:
https://github.com/blaskovicz/garmin...rce/GNCCApp.mc

When the widget loads, it will attempt to dynamically draw a summary of all information for the user (https://github.com/blaskovicz/garmin...SummaryView.mc) similar to these screenshots:
https://github.com/blaskovicz/garmin...ol#screenshots

My base class sets a simple layout (a header text label and a line) and then the rest of the info is draw in onUpdate() by subclass views. My problem is that when I run the widget on my physical watch (Fenix 5x) the screen is initially black with just the default @Strings.AppTitle at the top, before the rest of the layout / rendering code kicks in. Is there a way I can make this widget perform more like other watch widgets (ie it's not initially blank when it scrolls into view alongside other watch widgets)? When I run it in the simulator, it renders the initial view so quickly that I don't notice any issues.

This is my first Garmin app, so any pointers or help is appreciated. Thanks!
  • Former Member
    Former Member
    I believe this has been brought up several times before. Assuming you are not seeing that initial launcher-icon screen stick around for too long, longer than any other CIQ widget, then it is behaving as intended and you do not have control over it.

    Here are the last two threads that I remember it being mentioned:
    https://forums.garmin.com/forum/deve...ect-iq/159321-
    https://forums.garmin.com/forum/deve...in-widget-loop
  • This is a legacy thing from older/slower watches, where it showed the app name for CIQ widget when you went through the widget loop. It was so you could see which widget it was about to load and move on if it's not the one you want. You never see it in the sim.

    Update: Another thing you won't see in the sim is the widget timeout. On a watch, when a widget is shown, there is a timeout, where if there's no interaction with the widget for a period of time, they revert to the watchface. This timeout varies based on the the watch, from under a minute to about 2 minutes