The API was requiring developers to reschedule repeating tasks manually. For backwards compatibility this is still the default, but there is a new parameter that you can send to have Toodledo automatically reschedule repeating tasks for you.
In the editTask call, when you are completing (or uncompleting) a task, you can pass the new "reschedule=1" parameter and Toodledo will handle all the rescheduling for you.
This will simplify things.
If we wanted to find the task that was created, how would you suggest we do so?
I found a note in the API:
Each time you attempt a synchronization, your application should use the "getAccountInfo" API call. This will return two timestamps which you can use to determine if any further action is needed. The "lastaddedit" timestamp will indicate if any task has been added or edited. If this value has changed since the last time you checked, you can call "getTasks" and set the "modafter" parameter to fetch the tasks that have changed.
does including ...&reschedule=1 count as a synchronization?
Yes, any time you update or retrieve information, that is a synchronization, although this is really just a word that describes what you as a developer would do to keep your database in sync with our database. Toodledo's API doesn't really know when things are synchronized or not. That is for your app to determine.
Oh, and to find the newly created (rescheduled task), you can just do a search for newly added tasks with the same name.
This message was edited Jul 22, 2008.
You cannot reply yet
To participate in these forums, you must be signed in.