ToDoList in S60
The ToDoList provides access to the native To-Do
List database. The supported ToDo fields are the following:
Table 23: The supported ToDo fields
|
PIM API field
|
Corresponding Calendar Appointment field
|
Note
|
|---|
|
ToDo.SUMMARY
|
Subject
|
|
|
ToDo.NOTE
|
Description
|
|
|
ToDo.DUE
|
Due date
|
|
|
ToDo.PRIORITY
|
Priority
|
The values of the ToDo.PRIORITY integer field are
rounded to the valid values used by the underlying native database. The rounding
is done directly in the PIMItem.setInt() operation to
ensure that matching ToDos with PIMList.items(
matchingItem ) successfully matches by priority without the API
user needing to know the supported values. The supported values cannot be
reported to the API user explicitly.
|
|
ToDo.COMPLETED
|
Completed
|
The behavior of the ToDo.COMPLETED and ToDo.COMPLETION_DATE are
bundled together so that their values are kept in line with each other.
|
|
ToDo.COMPLETION_DATE
|
Completion date
|
See above.
|
|
Alarm
|
Alarm
|
This in an extended field in the S60 3rd edition Feature Pack 1
|
|
ToDo.CLASS
|
Synchronization
|
|
|
ToDo.UID
|
(Internal unique identifier)
|
|
|
ToDo.REVISION
|
(Internal last modification date)
|
|
Table 24: Extended
field identifiers
|
PIM API field
|
Numeric field identifier
|
Note
|
|---|
|
Alarm
|
0x1005001
|
The ToDo alarm field is a new feature in S60 3rd Edition Feature Pack
1. The value for this field is calculated from the ToDo.DUE field
in seconds. The alarm value cannot be negative, that is, it cannot be set
to the future.
The ToDo.DUE field is converted to midnight when
the item is written to the native database. On the PIM API side, the exact
time of ToDo.DUE can be added, but on the native side,
it is only possible to set the date of this field, not the exact time.
|
Unsupported in S60
ToDoList does not support any attributes.
ToDoList does not support categories.