Tickets :: [#7362] Windows Mobile : task with alarm

6.0.0-alpha12

6/6/25

Summary	Windows Mobile : task with alarm
Queue	Synchronization
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	jan (at) horde (dot) org
Requester	patrick.abiven (at) apitech (dot) fr
Created	09/19/2008 (6104 days ago)
Due
Updated	09/23/2008 (6100 days ago)
Assigned	09/23/2008 (6100 days ago)
Resolved	09/23/2008 (6100 days ago)
Milestone
Patch	No

09/23/2008 11:57:10 AM	Jan Schneider	Comment #5 State ⇒ Resolved	Reply to this comment
a) you are unconditionally overwriting the due date That is right. But in the case of windows mobile devices + funambol, we don't have the DUE attribute. So if we want to synchronize task with alarm, we have to initialize the DUE atttribute. I added a check to make sure that DUE hasn't been specified yet. b) nag's alarm only work if the alarm time is before the due date, i.e. if the time difference is greater than zero. It seems that not, because if alarm time == due date, Nag set the alarm to 1. So in our case, this workaround is useful. True. Committed, thanks!

09/23/2008 11:56:29 AM	CVS Commit	Comment #4	Reply to this comment
Changes have been made in CVS for this ticket: http://cvs.horde.org/diff.php/framework/SyncML/SyncML/Device/Sync4j.php?r1=1.56&r2=1.57&ty=u

09/23/2008 11:55:56 AM	Jan Schneider	Type ⇒ Enhancement State ⇒ Assigned Priority ⇒ 1. Low

09/23/2008 06:31:40 AM	patrick (dot) abiven (at) apitech (dot) fr	Comment #3	Reply to this comment
a) you are unconditionally overwriting the due date That is right. But in the case of windows mobile devices + funambol, we don't have the DUE attribute. So if we want to synchronize task with alarm, we have to initialize the DUE atttribute. b) nag's alarm only work if the alarm time is before the due date, i.e. if the time difference is greater than zero. It seems that not, because if alarm time == due date, Nag set the alarm to 1. So in our case, this workaround is useful. Regards Patrick

09/22/2008 09:59:57 PM	Jan Schneider	Comment #2 State ⇒ Feedback	Reply to this comment
That won't work because: a) you are unconditionally overwriting the due date b) nag's alarm only work if the alarm time is before the due date, i.e. if the time difference is greater than zero.

09/19/2008 09:50:34 PM	Jan Schneider	Assigned to Jan Schneider State ⇒ Assigned

09/19/2008 03:12:15 PM	patrick (dot) abiven (at) apitech (dot) fr	Comment #1 Priority ⇒ 1. Low State ⇒ Unconfirmed Patch ⇒ No Milestone ⇒ Queue ⇒ Synchronization Summary ⇒ Windows Mobile : task with alarm Type ⇒ Bug	Reply to this comment
Hello From a Windows Mobile + Funambol device, alarm of a task is not set into Horde database. Because, we only have a <ReminderTime> attribute, we should set the ALARM attribute but also the DUE attribute. Then nag/lib/Driver.php will set the alarm to 1. It seems that we should add, into lib/SyncML/Device/Sync4j.php, function sif2vtodo() if (!empty($a['ReminderSet'])) { + $vtodo->setAttribute('DUE', $iCal->_parseDateTime($a['ReminderTime'])); $vtodo->setAttribute('AALARM', $iCal->_parseDateTime($a['ReminderTime'])); } Regards Patrick