CIQ 3.2 - Wow!

On a watch, to access settings, when you are in the watch face selector (Long press up/watch faces on some devices), CIQ WF with local settings have a customize option.

What kind of errors are you seeing?  I have one in the works that goes right to a menu2, and I can exit in both the sim and on a real device with no probem.  I just pop the view in onBack in the menu delegate.

The exit is not the issue you can pop the view(s), on a F6X the user interaction is the trouble. Long press the menu button to open the settings, select the watch face selector, select your desired WF in the watch face selector, select the cumston settings option and then long press menu button a second time to open the WF settings of the menu2. This is not very handy.

My solution pushes directly the menu2 view to the stack when the settingsView is called with onUpdate. With this solution you avoid the second long menu button press and I do not need a BehaviorDelegate in the settingsView and handle every user interaction in the Menu2InputDelegate. This reduces the memory consumption a lot! To exit the menu2 and the settingsView I pop the view twice.

This works correctly on a F6X but not on the simulator. The watch directly enables the watch face including the new settings but the simulator doesn't go back to the watch face view and stay at the menu2.

My first opinion is that this cost too much memory and is only a small improvement. Maybe you could reduce the settings to the most relevant but you will always need the connect app to change all settings. I my opinion this makes no sense. All or nothing.

But let's have a deeper look into it and play around. ...maybe we will find much less memory consuming solution.

That's not what I see on a 945.

Long press up, then select on watch faces.

up/down to move to a watch face.

press select, and there is a menu with customize and apply. 

select on customize.

menu2 opened, and you can change what you want.

Back.

If it was the active WF, it's applied, if not, press select again and pick apply.

---

in the sim, Simulation>trigger app settings

menu opens

change whatever

back

watch face is shown with the new settings.

when you go to settings in the sim, the menu2 view gets pushed on top of the main view, and when you pop the menu in onBack, you go back to the main view.  The thing you have to do is make sure the main view sees the changes.  I do that by saving things i a class that's common to the main view and the menu2 view.

On the F6X the menu2 doesn't open directly by select on customize. The settings view is displayed with the ugly 'long press up button' message like the Analog watch sample implements. Very frustrating that again each device behaves different.

Nevertheless my solution seems to be very memory optimized but needs to be verified on other devices. (e.g. for 10  toggle menu items i added 15 lines of code, the items + onSelect + onBack)

I've found an even better solution... do not implement an extra settings view simply use the menu2 as view and return it. Then the simulator works correctly. jim_m_58 thanks for the discussion.

Yes, that's what I'm doing.  I go right to menu2.

    function getSettingsView() {
        return [new SLeanSettingsMenu(),new SLeanSettingsMenuDelegate()];
    } 

, the Analog watch sample implements an extra settings view and opens the menu2 as an inner view. Maybe not the best example in the sdk.

Here's a WF with anti alias, garmin weather, and on device settings if you want to see this stuff in action:

https://apps.garmin.com/en-US/apps/c051f37a-8fad-4907-b124-0112fe010c91

a1234.garmin-

a1234.garmin said:

Please allow to specify folder to install such stuff and please specify the size of each element proposed to install.

I have not yet tried this, but you *might* be able to move the files to another volume and then use a directory junction to map the original location to the new location.

https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/mklink