Well, if the frame always auto-hid after 10 seconds, and the delay for idle-suspend was 15 seconds, then it would work. I personally believe that the frame should be hidden more agressively - whenever there's a user action that doesn't address it, and after a longish timeout around 10 seconds. In my experience with kids, hitting the frame key and then trying to interact with the activity and being unable to is one of the more common hangups.
(I'm afraid I don't understand the latest on suspend, but it's my understanding that there are some kind of "micro-suspend" periods which are separate from longer-term "idle suspend".) Jameson 2009/5/3 <p...@laptop.org> > sascha wrote: > > On Sat, May 02, 2009 at 05:39:21PM +0100, Martin Dengler wrote: > > > > [Clock behaviour in suspend] > > > But I take your point...the answer is: no, it's not easy (with my > > > simple patch). I'm not sure what the behavior should be (hide on > > > idle?!, come out of suspend once a minute?!), really. > > With the XO going into suspend automatically, it should at least > > indicate that the clock has stopped as well (and no, the pulsing power > > LED is not enough). Showing an old time is _much_ worse than not showing > > it at all. > > given martin's point about the battery level, wireless strength, > etc, all becoming stale as well, perhaps the best fix would be to > always hide the frame during idle suspend. as far as i know, > however, there's currently no mechanism for apps to learn that > idle suspend is imminent. > > paul > =--------------------- > paul fox, p...@laptop.org > _______________________________________________ > Sugar-devel mailing list > Sugaremail@example.com > http://lists.sugarlabs.org/listinfo/sugar-devel >
_______________________________________________ Sugar-devel mailing list Sugarfirstname.lastname@example.org http://lists.sugarlabs.org/listinfo/sugar-devel