Menu 2 menu item in-focus colour?

Apologies for posing newbie questions but it's been a while since I coded the custom menu and I can't find a way to manage the background colour of the menu item that's currently in focus.

On the F7 (in the sim and on the device) it has the same background as the other menu items,

but on the 965(sim and device) the background colour is reversed, making the text unreadable:

Which Instance Method should I use to ensure the menu item in focus is readable?

Top Replies

  • Also, I haven't played with CustomMenu much, but can you just avoid setting the foreground/background colour altogether on your menu items? That way, hopefully your menu items will just…

All Replies

  • Thanks for the context!

    Yeah, as flocsy and others have mentioned, it sure would be nice if Connect IQ could tell us what the background colour is supposed to be, in certain situations. (Although in some cases it wouldn't help, if the background colour is dynamic yet the feature in question is static - e.g. app launcher icon.)

    I think it's pretty interesting that Garmin clearly wants us to make apps which follow the native look and feel of devices, but they sure don't make it easy. (See my example above about ALL CAPS vs Title Case for data fields).

    I just think CIQ is kind of an afterthought for Garmin as a whole. The only crucial apps seem to be:

    - certain supplemental Garmin apps

    - certain partner apps (Strava Relative Effort?)

    - paid Garmin watchfaces

    - Spotify, YouTube Music and other big-name music providers

    It probably also helps that monetization is limited to newer devices, so anyone who devs paid apps doesn't have to worry about a bunch of legacy issues like Menu2 having a white background on some devices.

    Ofc, going beyond monetization, CIQ as a whole has abandoned older CIQ 3 devices, in the sense that they no longer receive CIQ feature updates. This is after a few years where CIQ would receive new features for both CIQ 3 and CIQ 4 devices (which is the reason for the "System Level" versioning scheme).

    And I noticed YouTube Music (initially released more recently than Spotify) doesn't support certain older devices which are supported by Spotify.

    Some of the headaches that CIQ devs encounter can probably be avoided by simply targetting the latest and greatest devices. (Like that bug with Menu - not Menu2 - on certain old devices such as Fenix 5 and FR935, where the menu title says "English" instead of the string that you actually set.)

  • I guess Garmin actually does tell us what colours to use, at least for devices which support the personality library [*].

    [*] This seems to be every device which has CIQ 3.4 and higher.

    That's not so bad, as it includes several devices which aren't getting firmware updates anymore, like FR945LTE and Fenix 6 series. Fenix 6 is 6 years old at this point.

    (This goes back to how Garmin would probably prefer if we just focused on new devices)

    https://developer.garmin.com/connect-iq/personality-library/colors/

    You can see these constants in a built project at:

    [project root]\bin\gen\[part number]\source\Rez.mcgen

    You can also see these contants in ConnectIQ\Devices\[device id]\personality.mss