Gordon Williams

> Just use a category other than 'app'. Yes, that's the easiest - ideally we just do a PR to change the relevant apps for everyone. If you needed it...

I just checked and this works fine in slopeclock++ **I can also reproduce this exact error in BW Clock without the sunrise widget** - just right after starting the clock,...

Thanks for checking up on this - I think it's probably best to keep https://github.com/espruino/BangleApps/commit/8425f0b50aea39a9083b95ccc9f4211d9c5d556a and change BWClock/etc? Requiring the redraw in `show` seems like it's probably going to bite...

Yes, I think `load()` is best as there's no global way to ensure the screen is redrawn.

The 12x20 font issue is pretty easily solved, *but* my understanding is that sleep log uses *lots* of RAM. Enough that it can be an issue even on Bangle.js 2....

... also if using clock_info it should probably remember what setting it was scrolled to last time the clock was shown

Ok, just added something... So as an example: ``` var clockInfoMenu = require("clock_info").addInteractive(require("clock_info").load(), (itm, info) => { var x = 20, y = 20, w=80, h=48; g.reset().clearRect(x,y,x+w-1,y+h-1); g.drawRect(x,y,x+w-1,y+h-1); // debug...

@peerdavid any thoughts on this? How does this fit with what you're doing with clock_info at the moment? I think we should probably do with `.focus/.unfocus` methods exported, so clocks...

> should something be appended to the [Clock Faces guide](https://espruino.com/Bangle.js+Clock)? Yes, absolutely! And it might be worth mentioning the clock module too

It basically abstracts the user interaction away, so you call it and then all you have to worry about is drawing the information. Swiping on the watch screen then cycles...