View Single Post
Old 08-24-2010, 05:09 PM   #11
Iņigo
Guru
Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.Iņigo did not drink the Kool Aid.
 
Posts: 730
Karma: 72743
Join Date: Feb 2008
Location: Here or there
Device: iRex iLiad, iRex DR800S. K4NT. Kobo Aura, Aura One, Libra 2.
Quote:
Originally Posted by CoolDragon View Post
Do you mean to update the clock every 30 seconds? The only concern is that a local refresh on e-ink might cause some "ghost" effect (leftover from previous drawing). But the cycling status icon seems to handle this pretty well. Otherwise, 30 seconds seems to be good enough.
Yes, I mean that.
I don't think refresh will be a problem, for my little demos in lua. But I haven't tested it on the real device.

Quote:
1. font size
2. to bold or not to bold
Well, I prefer the second screen shot, but it's just personal.

3. space between clock and icons
I would vote for this.
Hehe. We have different tastes. Anyway let's exercise democracy, let's vote
By now:
option a (first screenshot: big, no space): 1
option b (second screenshot: bold, space): 1

Quote:
4. should clock be part of menu button like original "Menu"? i.e. a label or a button with a label inside?
I would say yes, which makes it easier to click the menu icon.
ok, I'm changing the code now.

Thanks for the feedback,
Iņigo
Iņigo is offline   Reply With Quote