Windows Mobile : task with alarm

Hello From a Windows Mobile + Funambol device, alarm of a t

Fri, 19 Sep 2008 15:12:15 +0000

Hello From a Windows Mobile + Funambol device, alarm of a task is not set into Horde database. Because, we only have a 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

That won't work because: a) you are unconditionally overwri

Mon, 22 Sep 2008 21:59:57 +0000

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.

> a) you are unconditionally overwriting the due date That

Tue, 23 Sep 2008 06:31:40 +0000

> 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

Changes have been made in CVS for this ticket: http://cvs.h

Tue, 23 Sep 2008 11:56:29 +0000

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

>> a) you are unconditionally overwriting the due date > Th

Tue, 23 Sep 2008 11:57:10 +0000

>> 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!