| 2015-04-22 20:03:41 |
Michael Zanetti |
bug |
|
|
added bug |
| 2015-04-22 20:07:18 |
Michael Zanetti |
description |
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.
Here's an countdown app for testing that sets a countdown to 20 secs from now: lp:~mzanetti/+junk/stopwatch-countdown |
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 |
|
| 2015-04-22 20:08:17 |
Michael Zanetti |
summary |
alarms have minute-precision only, should be seconds |
alarms sceduled within the current minute trigger immediately |
|
| 2015-04-22 20:08:35 |
Michael Zanetti |
description |
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 |
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 |
|
| 2015-05-01 07:48:51 |
Charles Kerr |
indicator-datetime (Ubuntu): status |
New |
Triaged |
|
| 2015-05-01 07:49:09 |
Charles Kerr |
indicator-datetime (Ubuntu): importance |
Undecided |
Medium |
|
| 2015-05-01 07:49:12 |
Charles Kerr |
indicator-datetime (Ubuntu): assignee |
|
Charles Kerr (charlesk) |
|
| 2015-11-08 21:34:22 |
Bartosz Kosiorek |
marked as duplicate |
|
1480200 |
|
