@gaperton I've now implemented Ionic Views into my WIP app - thanks a lot for your effort and for sharing!
Took a little bit of head-scratching over how to link up the screen to buttons in the .gui, and then a whole bunch more to get button taps to work via onclick (onactivate doesn't seem to work at all?), but I got there in the end.
I would recommend extending screen2 in your demo to show how to use a button, if you would be so kind.
@Tjeerd As for your "back button in views" question, if you're asking how to use the physical back button on the watch, I've just a few minutes ago added this using a bit of help from https://community.fitbit.com/t5/SDK-Development/Physical-Button-Exit-App/m-p/2385358/highlight/false...
Not sure if this is the correct/ideal way, but I edited view.js to change the current ({ key }) setup for onkeypress to a regular function(e), so it all looks like this:
document.onkeypress = function(e) {
e.preventDefault(); // We don't want the OS to do the normal actions when we press the physical buttons, as this would close the app when pressing "back", etc.
if( e.key === 'down' ) app.onKeyDown();
else if( e.key === 'up' ) app.onKeyUp();
else if( e.key === 'back' ) app.onKeyBack();
}
}
onKeyDown(){
this.screen.onKeyDown();
}
onKeyUp(){
this.screen.onKeyUp();
}
onKeyBack(){
this.screen.onKeyBack();
}
Then, in my screen's .js I simply have
this.onKeyBack = () => { console.log( 'planWorkout -> Home'); Application.switchTo('Home'); }
in my onMount().
