Although many of the timestamps in API2.0 are GMT Unix timestamps, some of them seem to be local times. These are start date / time, due date / time, and completed date. This is good, but it's not what it says in the documentation.
duedate : A GMT unix timestamp for when the task is due. The time component of this timestamp will always be noon.
duetime : A GMT unix timestamp for when the task is due. If the task does not have a time set, then this will be 0. If the task has a duetime without a duedate set, then the date component of this timestamp will be Jan 1, 1970.
All dates and times are stored as GMT. You set it as 11:00 and then retrieve it as 11:00. You should not have to adjust this by your timezone. The task will always be due at 11:00 no matter where you are. This is what is called a "floating time", since it is 11:00 in whatever timezone you are in.
Yes this is a floating timestamp, not a GMT timestamp. I guess that's what you meant, but it's confusing for a developer (me, anyway!). Because I have to convert other times between local time and GMT time, but I don't have to do that with due times. So it would be clearer if the documentation didn't say GMT.
Anyway Toodledo does exactly what we want it to do, so thanks for the clarification.
You cannot reply yet
To participate in these forums, you must be signed in.