[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Detection of hibernation wake-up
From:       "David Jarvie" <djarvie () kde ! org>
Date:       2008-10-23 12:40:28
Message-ID: 24ea326d9613171323778a69e4f8fdd7.squirrel () www ! sensical ! net
[Download RAW message or body]

On Wednesday 22 October 21:07, Aaron J. Seigo wrote:
> On Wednesday 22 October 2008, Thiago Macieira wrote:
>> I don't know what happens to the monotonic clock when the system
>> hibernates. But one has to wonder if a timer that expired during the
>> hibernation still makes sense...
>
> for dataengines in plasma it means "there's a pending data update
> request".
>
> for a trivial example of where this affects us, a clock that only shows
> the minutes only fires it's timer once a minute (and does drift
> correction at that point to keep it aligned, of course). so if you
> hibernate at second N in the
> minute, you have to wait for 60-N seconds for the clock(s) to show the new
> correct time. (of course, if the clocks are showing seconds, it's 1000-N
> ms instead, not nearly as bad =)
>
> it's survivable, no doubt, but not great, and we run into this issue with
> a few engines in real-world practice already. so  a timer expiring during
> hibernation isn't completely meaningless.

KAlarm also needs to know if timers have expired during hibernation -
otherwise alarms are lost or delayed.

The best solution would I think be for QTimer to have an option to adjust
itself when the system wakes from hibernation. That way, apps wouldn't
have to bother doing their own wakeup detection in relation to timers -
the detection and adjustment would be done in one central point.

-- 
David Jarvie.
KAlarm author & maintainer.
http://www.astrojar.org.uk/kalarm

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]