Menu2 , onSelect ( item ) save .

Hi, I have a question.
Is it possible to use two storage types in Menu 2 == on Select(item)?
I think
Storage.setValue
Application.Properties.setValue.

The point is that I want to save something to the watch storage and have the transformations in Application.Properties.setValue.

Here is the shortcode:

public function onSelect(item) as Void {


        if (item instanceof WatchUi.IconMenuItem) {
            item.setSubLabel((item.getIcon() as colors).nextState(item.getId()));
        } else if (item instanceof WatchUi.ToggleMenuItem) {
            Storage.setValue(item.getId() as Number, item.isEnabled());
            Properties.setValue(item.getId() as Number, item.isEnabled()); 
        }

Thanks for the reply.

Top Replies

All Replies

flowstate over 1 year ago in reply to flocsy🤠

flocsy🤠 said:
military time format (which IMHO isn't 100% the same as the 24h setting)

It isn't an opinion, but a fact which is lost on most North Americans afaik. I think it's bc, in civilian life, we use neither the ISO standard 24 hour time format (as in Europe) or (North American) military time, so we don't bother to distinguish between the two, which is understandable. So North Americans just say "military time" whenever they see a time format that has 24 hours.

(I'm Canadian, and I've worked with Americans who reflexively say "military time" when we're discussing the 24 hour time format in a UI.)

If I search "military time vs 24 hour time" the very first result is a Garmin support article, funnily enough.

[https://www.google.com/search?q=military+time+vs+24+hour+time]

There's also this gem further down the results.

Also, it's funny that modern Garmin watches support 12h, 24h *and* military time formats, but of course Connect IQ only exposes a boolean device setting called is24Hour (I assume this flattens both 24h and military time into a value of true). Just another legacy CIQ limitation that will never be improved upon.

(Yes, I realize it made sense back in the day when devices only supported 12h and 24h time formats.)

flocsy🤠 over 1 year ago in reply to flowstate

I think that from the user's perspective it makes sense to have 2 booleans: is24h, displayColon, cause maybe someone likes: 434pm

Fred over 1 year ago in reply to flocsy🤠

Maybe it also makes sense because a lot of young people don't actually know (no irony) what a 24-hour time format is - like 20:00, but they know what a 12-hour time format - 8:00.
I distinguish only AM, PM..