On May 28, 2009 11:09:08 Aaron J. Seigo wrote: > On Thursday 28 May 2009, Chani wrote: > > > > PS: By the way, there is a bug about time configuration. By default, > > > > update interval of digital-clock plasmoid is 60 seconds when > > > > showSeconds is false, and 1 second if it's true. If you change time > > > > from clock kcm and showSeconds is false, digital-clock applet > > > > refreshes itself 1 minute later. Maybe updateInterval should be > > > > hardcoded as 1 second regardless of showSeconds variable. > > > > > > waking up 60x more often than necessary is a really good way to reduce > > > battery life. the clock doesn't update once a minute just because it's > > > lazy ;) > > > > > > as Daniel points out, the correct solution is a dbus signal (probably > > > from kded4) that we can listen to. > > > > I'd like to see any time-jump give all the dataengines a kick, actually. > > "any time jump" isn't possible without polling afaik. which isn't an > option.
lame. there's no way to get notified when the system time is changed? > > > we still (afaik) have the problem that coming out of suspend doesn't > > update the clock until the minute changes, and so on. I have an amusing > > screenshot of the clock and its tooltip disagreeing on the time. :) > > suspend is a different matter, however. we could do a forced "check your > timing" of all engines when we come out of suspend if the power manager has > such a signal for us to listen to. yeah, that'd probably do. there must be such a signal... right? -- This message brought to you by eevil bananas and the number 3. www.chani3.com
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
