You are reading a single comment by @halemmerich and its replies.
Click here to read the full conversation.
-
I think as a first step the implementation as a remove handler set for setUI is probably enough. It should be possible for apps like quicklaunch to just call setUI() to trigger the removal of the currently running main app.
I did a small demonstration of the combination of UI removal, @Sir_Indy s hidable widget bar, modified gpstrek/iconlaunch apps and widgets implementing an update method. This may be the loading-screen-less future ;)
Not yet bug free, far from optimal but very cool to see the Bangle be about as fast as my old Amazfit BIP S.
1 Attachment
halemmerich
Thinking out loud again: If unloading/eval becomes more common should the unloading function of apps be exported and be accessible by other apps? This way e.g. Quick Launcher or Pattern Launcher could utilize/facilitate faster app switching as well?
I've nearly got remove/unload and eval working between BWClock and Desktop Launcher correctly on my app loader now. There's still some small buildup in RAM usage though.
EDIT: BWClock code. Desktop Launcher code.