Help find my bug: on device settings

This is for a watchface, right?

beva said:

can I manipulate the Settings/Delete menu as well oops that's another question

No. But for Fenix 8 and newer watches, you can use the watch's native watchface editor in CIQ. So the user could configure your watchface the same way they configure native watchfaces.

beva said:

Actually I'd expect both to return to the Garmin generated Settings/Delete menu,

Which watch are you using?

I don't see this problem on my FR955, with on-device settings for either data fields or watchfaces.

Can you try the Simple Lean G2 watchface from jim_m_58? It has on-device settings and it doesn't have that problem on my watch. If it has that problem on your watch, maybe there's a problem with the watch firmware.

Yes, for a watchface.

The back button works fine with Jims Simple Lean G2 watchface.

So it has something to do with my sourcecode I guess. Without code tags because of error messages.

class ttrApp extends Application.AppBase {
private var _mainView;
[...]
public function getSettingsView() as [Views] or [Views, InputDelegates] or Null {
return [new $.ttrSettingsView(), new $.ttrSettingsDelegate()];
}

function onSettingsChanged() { // triggered by settings change in GCM
_mainView.updateProperties();
WatchUi.requestUpdate(); // update the view to reflect changes
}
[...]
}

var menu=null;

class ttrSettingsView extends WatchUi.View {

public function initialize() {
View.initialize();
menu = null;
}

public function onUpdate(dc as Dc) as Void {
if (menu == null) {
menu = new $.ttrSettingsMenu();
var menudelegate = new $.ttrSettingsMenuDelegate();
var sublabels;
var sublabel;
// Add menu items for demonstrating toggles, checkbox and icon menu items
if (hasBackgrounds) {
sublabels = [$.Rez.Strings.none,
[...]
];
sublabel = loadResource(sublabels[ttrbackgroundvalue+1]);
menu.addItem(new WatchUi.MenuItem(loadResource($.Rez.Strings.wallpaper), sublabel, :wallpaper, null));
}
sublabels = [$.Rez.Strings.hide,
[...]
];
sublabel = loadResource(sublabels[ttroverrideweeknumber+1]);
menu.addItem(new WatchUi.MenuItem(loadResource($.Rez.Strings.overrideweeknumber), sublabel, :overrideweeknumber, null));
sublabels = [$.Rez.Strings.none,
[...]
];
sublabel = loadResource(sublabels[ttrwarnings+1]);
menu.addItem(new WatchUi.MenuItem(loadResource($.Rez.Strings.warnings), sublabel, :warnings, null));
WatchUi.pushView(menu, menudelegate, WatchUi.SLIDE_IMMEDIATE);
}
}

}

class ttrSettingsDelegate extends WatchUi.BehaviorDelegate {

public function initialize() {
BehaviorDelegate.initialize();
}

public function onBack() as Boolean {
WatchUi.popView(WatchUi.SLIDE_DOWN);
return true;
}

}

class ttrSettingsMenu extends WatchUi.Menu2 {
    public function initialize() {
        Menu2.initialize({:title=>loadResource(Rez.Strings.settings)});        
    }
}

class ttrSettingsMenuDelegate extends WatchUi.Menu2InputDelegate {
    public function initialize() {
        Menu2InputDelegate.initialize();
    }

    public function onSelect(menuItem as MenuItem) as Void {
        var _id = menuItem.getId();
        switch (_id) {
            case :wallpaper :
                $.pushSubWallpaper();
                break;
            case :overrideweeknumber :
                $.pushSubOverrideweeknumber();
                break;
            case :warnings :
                $.pushSubwarnings();
                break;
        } 
    }

    public function onBack() as Void {
        WatchUi.popView(WatchUi.SLIDE_DOWN);
    }
}

Thanks for posting your code!

Yeah it's happening because your settings view instantly pushes a 2nd view (the main menu view).

So the flow is:

user opens watchface menu > user selects Customize > ttrSettingsView is pushed (by the firmware / getSettingsView) > main menu view is pushed (by your app / ttrSettingsView)

This explains why the user has to press back twice at your main menu, but not why a single swipe right works. The first press of BACK pops the main menu, and the second press pops trSettingsView.

To fix this, getSettingsView() should directly return the main menu.

user opens watchface menu > user selects Customize > main menu view is pushed (by the firmware / getSettingsView)

You should move all the code from trSettingsView.initialize() to getSettingsView(). Once you've done that, you don't need trSettingsView or ttrSettingsDelegate.

class ttrApp extends Application.AppBase {
    private
    var _mainView;
    [...]
    public
    function getSettingsView() as[Views] or[Views, InputDelegates] or Null {
        var menu = new $.ttrSettingsMenu();
        var menudelegate = new $.ttrSettingsMenuDelegate();
        var sublabels;
        var sublabel;
        // Add menu items for demonstrating toggles, checkbox and icon menu items
        if (hasBackgrounds) {
            sublabels = [$.Rez.Strings.none,
                [...]
            ];
            sublabel = loadResource(sublabels[ttrbackgroundvalue + 1]);
            menu.addItem(new WatchUi.MenuItem(loadResource($.Rez.Strings.wallpaper), sublabel,: wallpaper, null));
        }
        sublabels = [$.Rez.Strings.hide,
            [...]
        ];
        sublabel = loadResource(sublabels[ttroverrideweeknumber + 1]);
        menu.addItem(new WatchUi.MenuItem(loadResource($.Rez.Strings.overrideweeknumber), sublabel,: overrideweeknumber, null));
        sublabels = [$.Rez.Strings.none,
            [...]
        ];
        sublabel = loadResource(sublabels[ttrwarnings + 1]);
        menu.addItem(new WatchUi.MenuItem(loadResource($.Rez.Strings.warnings), sublabel,: warnings, null));
    
        return [menu, menudelegate];
    }

    function onSettingsChanged() { // triggered by settings change in GCM
        _mainView.updateProperties();
        WatchUi.requestUpdate(); // update the view to reflect changes
    }
    [...]
}

Thanks, I guess I now understand the problem!

It's fixed, thanks again!

return false in onBack()

That toke me to the blue triangle of death.

At least in the simulator it did, so I didn't try it on my watch :D

in the sim? That means you exited your main view (the las one in the pile of views, or usually the 1st one you opened in getInitialView) On a real device it just exits the app.