[prev in list] [next in list] [prev in thread] [next in thread] 

List:       horde-bugs
Subject:    [Tickets #10014] Snooze and dismissal for Sunbird/Lightning
From:       bugs () horde ! org
Date:       2011-04-29 20:52:06
Message-ID: whups-10014-40da5920f32557c0a3e3eec1fb8a2e62 () bugs ! horde ! org
[Download RAW message or body]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/10014
------------------------------------------------------------------------------
  Ticket             | 10014
  Created By         | spamstop1@terriertech.com
  Summary            | Snooze and dismissal for Sunbird/Lightning
  Queue              | Kronolith
  Version            | Git master
  Type               | Enhancement
  State              | New
  Priority           | 2. Medium
  Milestone          |
  Patch              | 1
  Owners             |
+New Attachment     | Snooze.patch
------------------------------------------------------------------------------


spamstop1@terriertech.com (2011-04-29 20:52) wrote:

I posted the following to Ticket #7470 then realised that ticket was  
for the 2.3 queue.

I could not see a good solution to the snooze/dismiss problem without  
storing the snooze info with the event.  Therefore, I added an  
event_snooze varchar column to  kronolith_events.  See attached patch  
(relative to 3.0.2-git).

This seems to work for dismiss, snooze (including multiple successive  
snoozes, in limited testing), and recurring events (if the LASTACK  
occurs before one occurrence, then Thunderbird views the following  
occurrence as not ACKed).  It also seems to work OK on multiple  
Thunderbird clients in the same timezone, i.e. snoozing on one client  
will auto-dismiss the alarm on other clients next time they reload the
calendar.

Hope this helps.





-- 
You are subscribed to this list as: horde-bugs@progressive-comp.com
To unsubscribe, mail: bugs-unsubscribe@lists.horde.org
[prev in list] [next in list] [prev in thread] [next in thread]