It's all we have atm. I could imagine it as a timer api but it would probably require better precision (it's off up to 5 seconds in some cases atm) and some other fixes (like calling back the originating app on clicking the notification, instead of the clock app). Also it has the side effect that such timers will show up as alarms in the datetime indicator and iirc the clock app. Both of them are probably questions for design. On the other hand, a proper timer api could offer better features I think. Depends if we want to allow, e.g. focusing/resuming the app when the timer is due so other things could be done instead of just ringing a notification.
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1480200 Title: indicator-datetime starting ringing almost immediately if timer is set in current minute Status in Client Developer Experience: New Status in Canonical System Image: Incomplete Status in Timer: Confirmed Status in Ubuntu Clock App: Incomplete Status in indicator-datetime package in Ubuntu: Confirmed Bug description: indicator-datetime doesn't check seconds for alarms. Steps to reproduce: 1. Install Timer: https://uappexplorer.com/app/timer.mivoligo 2. Set timer to 15 seconds in current minute 3. Start timer Currently: 4. Alarm is ringing almost immediately (it is not always reproducible) Expected: 4. Alarm is ringing after 15 seconds It is an blocker for Timer implementation in Clock app: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1427566 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-developer-experience/+bug/1480200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
