Alarms fetched in Alarms API are getting their date from the due date, which is the due date of the next occurrence. The question is whether I get a proper date at fetch time if I do not set the due date for the original event. Or is the due date for the individual occurrences set independently from the original event's due date? If yes, we can make the change in UITK Alarms API.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1283859 Title: Updated recurring alarm values are not reflected in the indicator until phone reboot To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1283859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
