[reesd]

Hi,

Can someone describe how the @modified attribute in the OTL XML is used. It looks like it gets created when an item is modified and perhaps the value indicates what was modfied? Then I guess its somehow used when synchronizing with the palm?
Here are two examples:

<item id="278624330" type="todo" priority="4" create-date="23 Oct 2006 14:38" last-modified="05 Nov 2006 19:32" percent-complete="0" pos-hint="278624236" modified="#8">
<text>look at second TV</text>
</item>
<item id="273817144" type="todo" priority="3" last-modified="05 Nov 2006 19:37" percent-complete="0" start-date="09 Sep 1999 00:00" due-date="09 Sep 1999 00:00" pos-hint="278624330" modified="#10">
<text>dated</text>
</item>

Thanks,

dave

[reesd]

How about a hint i/expressions/face-icon-small-wink.gif? Or am I in the wrong forum here?

I would hate to spend an hour reverse engineering something that one of your engineers could answer for me in about ten seconds.

I suspect it is what is giving me these errors/warnings also after I run a transform on an outline and sync. I am giuessing its because I am not setting the modified attribute the sync algorithim doesn't know which to pick (vs. using the more typical modified date approach).

Quote

---

The "Due Date" field of the task "fruit to work {S7D}" has been modified on both platforms. The value on the desktop is 11/13/06 00:00:00. The value on the handheld is 11/06/06 00:00:00.
The "Start Date" field of the task "review/batched - R - Life {S7D}" has been modified on both platforms. The value on the desktop is 11/16/06 00:00:00. The value on the handheld is 11/09/06 00:00:00.
The "Due Date" field of the task "review/batched - R - Life {S7D}" has been modified on both platforms. The value on the desktop is 11/16/06 00:00:00. The value on the handheld is 11/09/06 00:00:00.

---

Thanks,

d

[George]

The Bonsai Outline DTD in the 4.1 beta has comments for the modification field bit positions.