News for Widget Glances!

Up until now, glances were only on the f6 and marq devices, but yesterday beta fw for the 945 and 245 with glances was released (version 4.06 on both devices)!

  • The only difference I can see it, that the code, I listed above, has a background annotation in the main AppBase. May this interfere wit the glance annotation?

  • Jim, would be nice if I could get any ideas what's going wrong. As I said, I tried adding a glance view to another widget and this worked. For the other widget and can't bring my watch to show up. It seems whether the overwritten glance view isn't found and the default is used.

    Another problem: I described it here already but I currently have no clue whether it's the current FR945 beta in common or the glance view support of this beta version: I have a widget which reads timestamps from the object store (Time Tracker). Time tracker worked perfect since 15 months now. But with this beta version a sync via GCM resets all my timestamps. It is as if they were never stored. At first I thought it's the new glance view together with the memory limit. But now I am not sure any more.

  • I can't see anything.  Have you tried the println calls yet?  That would be the first thing I'd try.

  • Hi Jim,

    this is very strange. I asked a user to install my widget on his FR945. And he told me that he could see my glance view after installation. But then he activated the expert mode of my widget (it is an option setable via menu or via GCM), the glance view was gone. 

    I then tried things on my fr945 and I can't reproduce the steps but I was able to see the glance view on my watch, too. But now, it's gone again. IMO, this is very buggy....

    Maybe there is a problem with the delegate of my main app?

  • Something odd.  Maybe the delegate, or you're not handling things right between the glance and full screen.

    Again, println calls could help.

  • OK, I will try this with println calls. Here (click) is stated: These log files are not automatically created, so must be manually created on the device and named to match the name of the app’s corresponding PRG file. For example, to log output from /GARMIN/APPS/MYAPP.PRG, you must create /GARMIN/APPS/LOGS/MYAPP.TXT.

    How do I find my apps PRG name? I had a look in that directory and there are a lot of numbers .PRG listed? Do I have to find the right one or is it simply the name of the app? My widget is called "Battery Info" - What's with the space?

  • It's easiest if you test with a side load, as you know the name needed for the txt file.

  • Here we go: I placed println outputs everywhere in the initializes and in the getGlanceView() call. The getGlanceView() isn't called (Steps I did on the watch: Moved the carousel two times over the glance view, then entered the widget once and left it again.):

    getServiceDelegate() is called
    getServiceDelegate() is called
    onBackgroundData(data) is called
    getInitialView() of main app is called
    batteryInfoDelegate is initialized

  • You have glance view enabled on the watch?  What do you see with soming like the f6 target in the sim?

  • Sure, I have enabled it. And I can see exactly that. what my log shows and Garmin described in the programmers guide: If widget doesn’t override AppBase.getGlanceView(), default WatchUi.GlanceView will be used, which simply shows the name of the Widget.

    Using the F6 as target in the sim I can see the glance view (if enabled). I developed the glance view with the F6