Opened bug #1583639 for a real API
** Changed in: canonical-developer-experience
Importance: Undecided => Medium
** Changed in: canonical-developer-experience
Assignee: (unassigned) => Alejandro J. Cura (alecu)
** No longer affects: canonical-developer-experience
--
You received this b
** Changed in: canonical-developer-experience
Status: New => Confirmed
--
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 s
** Description changed:
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 no
@michael yeah so all of that make using the alarm api for this seem like
the wrong approach, and we should provide a proper timer api.
For example see
http://developer.android.com/reference/android/os/CountDownTimer.html
or perhaps
https://developer.apple.com/library/mac/documentation/Cocoa/Ref
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 s
Is the alarm api appropriate to support timers? or just all we have atm
** Changed in: canonical-devices-system-image
Status: New => Incomplete
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Pat McGowan (pat-mcgowan)
--
You received this bug notification bec
** Summary changed:
- indicator-datetime starting ringing almost immediately if timer is set for
less than 60 seconds
+ indicator-datetime starting ringing almost immediately if timer is set in
current minute
** Description changed:
indicator-datetime doesn't check seconds for alarms.
7 matches
Mail list logo