On Sun, May 03, 2009 at 09:01:14AM -0400, p...@laptop.org wrote:
> 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.

Given this, and the fact that frame icons don't get any useful
gtk.gdk.{VISIBILITY,EXPOSE} events more than once per Sugar session
(unless one changes VTs away and then back), don't expect an
acceptable clock (redraws when the frame is exposed and only then,
hides before power blanking) anytime soon.

If we want a clock before then, we're going to have to accept
something less than perfect.

> paul


Attachment: pgpQ9zuJCu0ld.pgp
Description: PGP signature

Sugar-devel mailing list

Reply via email to