EDIT: @halemmerich beat me to it, but I'll leave my comment as well.
I believe require('widget_utils').hide() could be introduced to Icon Launcher to add that functionality, called if full screen is set. require('widget_utils').show() should probably be added to it's remove-function in that case so that widget show on the clock when fast loading back.
On the other hand, if we set widget_utils.show() in the remove- function and fast load a clock that should be full screen it will get widgets if it itself doesn't tell widgets to hide. Maybe apps that utilize fast loading (clocks and launchers so far) should be expected to tell widgets to either .hide(), .show() or use .swipeOn()?
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.
EDIT: @halemmerich beat me to it, but I'll leave my comment as well.
I believe
require('widget_utils').hide()
could be introduced to Icon Launcher to add that functionality, called if full screen is set.require('widget_utils').show()
should probably be added to it'sremove
-function in that case so that widget show on the clock when fast loading back.On the other hand, if we set
widget_utils.show()
in theremove
- function and fast load a clock that should be full screen it will get widgets if it itself doesn't tell widgets to hide. Maybe apps that utilize fast loading (clocks and launchers so far) should be expected to tell widgets to either.hide()
,.show()
or use.swipeOn()
?Here is a tutorial on widget_utils.