Can I write one widget with glance view for all watches

I plan to write simple widget, icon, progress (line) text - so it' can be maybe ciq 1.x app

If I implement getGlanceView(), will this widget run for all watches? If no glance system shows view?

By the way is any place to see what functionality are implemented on each watch? My widget will show stress but on my f6 there is widget with stress and if this widget is on all watches I don't want to spend time unproductive.

  • on sim all devices are updated every second (6s,6, 6Spro, 6Pro)

    which device on sim has  Live_updates false to test?

    if something is annotated (:glance) is accessible for both glance and view?

  • if something is annotated (:glance) is accessible for both glance and view?

    Yes. It's similar to how something that has a ":background" annotation is included in both the main app and the background task. (As before this does not imply that the glance process and the normal process share the same memory or run in the same process. They just share some of the same code.)

    which device on sim has  Live_updates false to test?

    When I search for "liveUpdates": false in the devices folder, I see the following devices:

    fenix6, fenix6s, fr245, marq*

    The way I handle this in one of my apps (a stopwatch widget), is that I don't even implement a glance view for devices which don't support live updates (because for that app there's point in showing anything other than the default view which shows the app name.) I handle this by using jungle exclusions to have different code for live update devices and non-live update devices.

    on sim all devices are updated every second (6s,6, 6Spro, 6Pro)

    I just tried this with CIQ 3.2.5 and my stopwatch widget (after modifying it to implement a glance view for 6 and 6s) and I see the same thing. There must be a bug in the simulator because I could've sworn the last time I tried this it worked properly (6S and 6 did not have live updates in glance mode.)

    FR245 (non-music) has the same problem.

    Same problem with SDK 3.2.4 and 3.2.3. I tried with both Eclipse and VS Code and I see the same thing. Not sure what's going on here. (I use Windows, if that makes a difference)

    I would suggest filing a bug report.

  • I have looked for live_Updates as jim mentioned...

    I've tested for all which have false and all update every second on glance - it's bug I report it.

    So how it look on real watch?

    Can you test it on your watch (I have pro version) ? If you call requestUpdate every second, is glance updated every 30s?

  • I don't have a glance-enabled watch, I have a 935 :(.

    But the last time I checked in the sim (months ago), I could've sworn it worked as expected. (On a device with no live update support, like FR245 non-music, the glance view would not update every second.)

    I don't get how this would suddenly stop working, especially when it seems to have the same problem with older SDKs: 3.2.3 and 3.2.4.

  • I went all the way back to SDK 3.1.9 and live update support in the simulator works properly. A simulated FR245 does not have live updates, and a simulated FR245M has live updates.

    It seems that VS Code doesn't work properly unless you have SDK 3.2.3 or higher tho. You'll have to test with Eclipse :(.

  • there is big difference between  "suddenly stop working" and "work and update every 30 second"

    So what does it exactly mean:

    Devices that have less memory [2] will start the app only when the system deems it appropriate, and calls to WatchUi.requestUpdate()
    will have no effect. <------ NO EFFECT NO onUpdate????
    Such a device could update the ‘Glance Page’ when it becomes visible (activated) and
    at least 30 seconds since last update. <-------
    - WILL SYSTEM CALL onUpdate evry 30 sec?
    - can I call requestUpdate every sec but onUpdate  will call only evrey 30s?
    - I can't
    call requestUpdate every sec  and have to cal it every 35s?

  • there is big difference between  "suddenly stop working" and "work and update every 30 second"

    By "suddenly stop working", I'm talking about the *simulator*. I mean that it used to respect the liveUpdates flag and it doesn't. Clearly something broke after SDK 3.1.9.

  • should I instal sdk 3.1.9 to test this behaviour?

  • You can, but it doesn't support several newer devices like Enduro and FR745.

  • ok, i see how it run and assume that on real device will be the same