Persisting settings accross sessions for ConnectIQ widgets?

Within my widget, I would like to give the user the possibility to set certain settings and I'd like these settings to be remembered the next time the user starts the widget.

For example, let's say I have a widget which displays the atmospheric pressure in mmHg by default. When the user presses the Menu key within the widget, they are presented with a menu that allows them to choose a different measurement unit for displaying atmospheric pressure such as mm (In), milibars etc The issue I have is that the next time they start the widget, this setting will be lost and the pressure will once again default to mmHg.

Currently I'm using the code below for this and the issue is that the value of the pressureUnit variable will again default to "mmHg" next time I start the widget. How can I set this in such a way in the code so that the pressure unit value the user chooses is remembered on widget restart?

var pressureUnit = "mmHg";

class MenuTest extends Ui.MenuInputDelegate {
function onMenuItem(value) {
if( value == 0 ) {
pressureUnit = "mmHg";
}
else {
pressureUnit = "milibars";
}
}
}

Thank you very much!

Former Member over 10 years ago

loadProperty, getProperty, setProperty and saveProperty should do your job

http://developer.garmin.com/downloads/connect-iq/monkey-c/doc/Toybox/Application/AppBase.html

thebigbadwolf_1 over 10 years ago

Thanks pmprog that's definitely what I needed! :)

Another question, is the below the correct way to set the property from the view? (sorry if this is a dumb question, in my defense I'm not a programmer, more like a GPS device enthusiast using my limited programming knowledge to add some functionality to my fenix3).

class MenuTest extends Ui.MenuInputDelegate {
function onMenuItem(value) {
if( value == 0 ) {
App.AppBase().setProperty("pressureUnit", "mmHg");
}
}
}

Former Member over 10 years ago

Not quite, you should use:

App.getApp().setProperty("pressureUnit", "mmHg");

Former Member over 10 years ago

I'm not sure if there were other factors, meaning that this might not always be necessary, but I would recommend that you load the values at startup & save on exit. I experienced memory leaks that appear to be attributed to pushView/switchToView after setProperty has been called.

thebigbadwolf_1 over 10 years ago

Thanks very much pmprog! Works like a charm. :)

@SHARKBAIT_AU, thanks for the tip, I'm currently running the widget on my fenix 3, will check if any memory issues.