View Single Post
Old 08-10-2011, 03:25 PM   #17
the.Mtn.Man
Guru
the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.the.Mtn.Man ought to be getting tired of karma fortunes by now.
 
the.Mtn.Man's Avatar
 
Posts: 710
Karma: 2483502
Join Date: Jul 2011
Device: Kobo Aura
Quote:
Originally Posted by MDK View Post
No, that falls within the same use case. The device suspends regardless of what menu is open. So say we update the time when you open the menu. You are allowed to open the reading menu and leave it open and the clock would appear 'stuck' from the user's perspective.
How accurate do you think it needs to be? Showing anything within a minute or two of the actual time should be sufficiently accurate for most people.

And again I'll note that updating just the pixels that make up the clock display once every minute would use an inconsequential amount of energy.
the.Mtn.Man is offline   Reply With Quote