touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #58789
[Bug 1426361] Re: Alarms API should expose a unique permanent alarm ID that clock app can use to open an alarm
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1426361
Title:
Alarms API should expose a unique permanent alarm ID that clock app
can use to open an alarm
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Bug description:
Alarms API should expose a unique permanent alarm ID that clock app
can use to open an alarm instead of just the alarm index that varies
based on the alarm date dynamically.
Use Case: Bug 1387210 Indicator-datetime will pass the
QOrganizerItemId (unique alarm ID) to clock app when the user clicks
on an alarm in the indicator-datetime. But the current Alarms API does
not allow clock app to open the alarm using that unique ID which
results in clock app not knowing which alarm to show to the user.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1426361/+subscriptions
References