Summary: | update clock immediately after waking up from sleep | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Nick Shaforostoff <shafff> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | 1lukas1, alan.christopher.jenkins, andresbajotierra, bastian.voigt, chalkerx, kde, pascal, petr.ohlidal, toralf.foerster |
Priority: | NOR | ||
Version: | 4.1 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Nick Shaforostoff
2008-09-15 20:21:33 UTC
An alternative might be to use a QT equivalent of the POSIX clock_nanosleep(CLOCK_REALTIME, TIMER_ABSTIME, &next_minute, NULL) In other words, perhaps there's some way to wait for "the next minute" on the system clock, instead of (or in addition to) waiting for 60 seconds subjective time. Do you think this should be marked as duplicate of bug 181380 ? Thanks no it isn't. both bugs require calling same slot in clock widget, though ;) *** Bug 197233 has been marked as a duplicate of this bug. *** *** Bug 199404 has been marked as a duplicate of this bug. *** *** Bug 222421 has been marked as a duplicate of this bug. *** *** Bug 228217 has been marked as a duplicate of this bug. *** Also, you could check each second, if the date/hour/minute had been changed unexpectedly since last check. (e.g. minute-change at second 33). Of course, this is not as pretty as a signal from solid, should such exist. *** Bug 235463 has been marked as a duplicate of this bug. *** related to bug 181380 ( which have some more infos ) *** This bug has been marked as a duplicate of bug 181380 *** *** Bug 285436 has been marked as a duplicate of this bug. *** |