The fix for this bug, under the current assumptions: have datetime hide
all VTODO items that don't have audio urls. That fix would come back to
bite us once we start importing other VTODOs from external calendars.
IMO what we need is a way to flag this special treatment for our clock-
app alarms without breaking third-party vtodo events.
I suggest we add an "x-canonical-disabled" tag to disabled alarms:
1. it gives datetime sufficient info to not process the alarms
2. qtorganizer5-eds seems to already support QOrganizer tag <-->
ECalComponent category conversion,
3. This would let ubuntu-ui-toolkit clean up a wart of it
deleting/restoring attachments as a proxy for an enabled/disabled flag
4. It doesn't break third-party VTODOs
5. It simplifies the fix for bug #1362341 (OneTime alarms are not
automatically dismissed or delete after they are triggered)
** Also affects: ubuntu-ui-toolkit
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Unity API
bugs, which is subscribed to Indicator Date and Time.
https://bugs.launchpad.net/bugs/1361702
Title:
Disabled alarms show up as calendar events
Status in The Date and Time Indicator:
Triaged
Status in Ubuntu UI Toolkit:
New
Bug description:
When you disable an alarm in the new clock app (with white
background), it causes the alarm to show up as a calendar event. The
expected behaviour is to not show up at all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1361702/+subscriptions
--
Mailing list: https://launchpad.net/~unity-api-bugs
Post to : unity-api-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~unity-api-bugs
More help : https://help.launchpad.net/ListHelp
