https://bugs.kde.org/show_bug.cgi?id=463278
David Jarvie changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/pim/
|
https://bugs.kde.org/show_bug.cgi?id=463278
--- Comment #6 from Rickard Westman ---
That sounds like a good idea! Perhaps rounding to the nearest minute (rather
than truncating) would also be a rather simple change, cutting the relative
error in half?
--
You are receiving this mail because:
https://bugs.kde.org/show_bug.cgi?id=463278
--- Comment #5 from David Jarvie ---
It would require a significant redesign to trigger alarms at times other than
on a minute boundary. Given that this would be very much a minority
requirement, the most that I could contemplate doing would be to add
https://bugs.kde.org/show_bug.cgi?id=463278
--- Comment #4 from Rickard Westman ---
It's not really stopwatch accuracy I expect, but more like kitchen timer
accuracy. An alarm set for 2 minutes should not trigger after 1 minute. An
alarm set for 1 minute should not trigger after 0 seconds. So
https://bugs.kde.org/show_bug.cgi?id=463278
--- Comment #3 from David Jarvie ---
KAlarm was never intended as a high accuracy timer, but rather as an
application to help people organise their lives and remember to do things. I
can see that if you expect it to act as a stopwatch you will get a
https://bugs.kde.org/show_bug.cgi?id=463278
--- Comment #2 from Rickard Westman ---
I understand the technical reason, but when you can set an alarm for 1 minute
and it fires after 1 second, it strains belief that any non-developer could see
that as expected and intended behavior. So even if
https://bugs.kde.org/show_bug.cgi?id=463278
David Jarvie changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
