Public bug reported:
Use case: a countdown timer.
As an app might be suspended by the time the countdown hits 0, currently
the alarm api is the only way to create such apps. However, for that use
case there would be a requirement for second-precision at least.
Currently, when a countdown is set to some few seconds, staying within
the current minute, the alarm will trigger immediately when it is synced
to the datetime-indicator, instead of waiting for the time to trigger.
If the alarm is longer, passing the next minute, it seems to actually
trigger it on the right time.
Here's an countdown app for testing that sets a countdown to 20 secs
from now: lp:~mzanetti/+junk/stopwatch-countdown
** Affects: indicator-datetime (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Use case: a countdown timer.
As an app might be suspended by the time the countdown hits 0, currently
the alarm api is the only way to create such apps. However, for that use
case there would be a requirement for second-precision at least.
+ Currently, when a countdown is set to some few seconds, the alarm will
+ trigger immediately when it is synced to the datetime-indicator, instead
+ of waiting for the time to trigger.
+
+ If the alarm is longer, passing the next minute, it seems to actually
+ trigger it on the right time.
+
Here's an countdown app for testing that sets a countdown to 20 secs
from now: lp:~mzanetti/+junk/stopwatch-countdown
** Summary changed:
- alarms have minute-precision only, should be seconds
+ alarms sceduled within the current minute trigger immediately
** Description changed:
Use case: a countdown timer.
As an app might be suspended by the time the countdown hits 0, currently
the alarm api is the only way to create such apps. However, for that use
case there would be a requirement for second-precision at least.
- Currently, when a countdown is set to some few seconds, the alarm will
- trigger immediately when it is synced to the datetime-indicator, instead
- of waiting for the time to trigger.
+ Currently, when a countdown is set to some few seconds, staying within
+ the current minute, the alarm will trigger immediately when it is synced
+ to the datetime-indicator, instead of waiting for the time to trigger.
If the alarm is longer, passing the next minute, it seems to actually
trigger it on the right time.
Here's an countdown app for testing that sets a countdown to 20 secs
from now: lp:~mzanetti/+junk/stopwatch-countdown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1447332
Title:
alarms sceduled within the current minute trigger immediately
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1447332/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
