aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCharles Kerr <charles.kerr@canonical.com>2015-04-06 14:58:34 -0500
committerCharles Kerr <charles.kerr@canonical.com>2015-04-06 14:58:34 -0500
commitaa3ee9ce63f3fb92b548593d03dd427f59c33ce5 (patch)
tree4dae9fa83c06690b650aa3b0ef1bae8ffeb70919
parent7feb72952529269b9d6e8be2e04e992acb8812c7 (diff)
downloadayatana-indicator-datetime-aa3ee9ce63f3fb92b548593d03dd427f59c33ce5.tar.gz
ayatana-indicator-datetime-aa3ee9ce63f3fb92b548593d03dd427f59c33ce5.tar.bz2
ayatana-indicator-datetime-aa3ee9ce63f3fb92b548593d03dd427f59c33ce5.zip
in the EDS engine, give a better explanation in the comments how we handle alarms with no triggers, and why
-rw-r--r--src/engine-eds.cpp6
1 files changed, 4 insertions, 2 deletions
diff --git a/src/engine-eds.cpp b/src/engine-eds.cpp
index 4435bdf..474bac5 100644
--- a/src/engine-eds.cpp
+++ b/src/engine-eds.cpp
@@ -581,8 +581,10 @@ private:
e_cal_component_alarms_free(e_alarms);
}
- // hm, no alarms? if this came from ubuntu-clock-app,
- // manually add a single alarm for the todo event's time
+ // Hm, no alarm triggers?
+ // That's a bug in alarms created by some versions of ubuntu-ui-toolkit.
+ // If that's what's happening here, let's handle those alarms anyway
+ // by effectively injecting a TRIGGER;VALUE=DURATION;RELATED=START:PT0S
else if (appointment.is_ubuntu_alarm())
{
Alarm tmp;