[Panel-devel] dataengines and timing revisited
Alex Merry
huntedhacker at tiscali.co.uk
Thu Aug 30 11:54:29 CEST 2007
On Thursday 30 Aug 2007, Aaron J. Seigo wrote:
> remaining caveats: the clock has an interesting problem where it
> really wants to pin the ticks to clock ticks, especially for the
> minutes-only ... i have yet to figure out how to arrange that.
> without it, it is possible for the ticks to drift dramatically so
> that the time is up 59s out. maybe it's just me, but that would suck
> =) if someone provides a clock that just shows the hour, that could
> be even worse. then again, perhaps the clock, as a special case, just
> continues to manage its own update ticks.
My first thought would be for the data source to update internally every
half-second. Applets could request updates at 1s, 1min, 1h, 1d, etc.
intervals (round the setUpdateFrequency value up?), and those would be
passed when the second, minute or hour (respectively) changes.
When the shortest requested update frequency every minute or hour, you
could even possibly do some complicated optimisations where it, for
example, put a timer (ie: slept) for 58s, then checked the time every
half-second until it changed and then push out the update and put the
timer back on.
Of course, this might not be possible or have a ton of issues I haven't
spotted - I'm still quite green, and I'm currently a month out of date
on plasma architecture.
Alex
--
KDE: http://www.kde.org
Ubuntu/Kubuntu: http://www.ubuntu.org http://www.kubuntu.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/panel-devel/attachments/20070830/3a1d2a0d/attachment.pgp
More information about the Panel-devel
mailing list