Just to confirm @user141359 - this only happens when you go to the launcher and then back again from the launcher, without running an app from it?
In combination with a launcher implementing setUI with remove handler that would currently be expected.
Argh, that's frustrating. I don't know why I didn't fully appreciate that when I changed the default launcher.
@halemmerich I guess we've got your changes to loadWidgets (with hiding) that could be used? Or I guess we could have the launchers only do a fast load if the clock app contains the text Bangle.loadWidgets?
I'm also wondering whether maybe I should just implement the hideable widgets library (using overlays) and then include that in any clocks that don't explicitly load widgets? It wouldn't work for clocks that aren't in the app loader though
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Just to confirm @user141359 - this only happens when you go to the launcher and then back again from the launcher, without running an app from it?
Argh, that's frustrating. I don't know why I didn't fully appreciate that when I changed the default launcher.
@halemmerich I guess we've got your changes to
loadWidgets
(with hiding) that could be used? Or I guess we could have the launchers only do a fast load if the clock app contains the textBangle.loadWidgets
?I'm also wondering whether maybe I should just implement the hideable widgets library (using overlays) and then include that in any clocks that don't explicitly load widgets? It wouldn't work for clocks that aren't in the app loader though