ForumsSearch



Search results for "Posted by bengt.mansson"
Author Message
bengt.mansson

Score: 1
Sadly it is a bug ignored by Toodledo, who seems to blame Outlook.

I spent a few minutes to test.

A test event imported from Toodledo into Outlook have this data:
DTSTART;VALUE=DATE:20150513
DTEND;VALUE=DATE:20150513

An identical event exported from IOS have this data:
DTSTART;VALUE=DATE:20150513
DTEND;VALUE=DATE:20150514
Re-exporting the first event from IOS also give the same data as the second one.

That date difference makes it appear as an all-day event instead of a zero-time event at midnight.

Maybe other calendars are more clever than Outlook to work-around format bugs at import but that is no excuse.
Clearly Toodledo should be able to export in the same way as other calendars.
bengt.mansson

Posted Jan 31, 2012 in: Timezone problems with duetime
Score: 1
a related issue:
API doc says:
duedate : ... When fetching from the server, it will always be noon.

My experience is that it is not noon. It's midnight.

Well, actually I've not checked the POST responses but in the iCal that I can import into Outlook it is midnight.
That is bad because I want my week view focused on working hours.

Is there any setting I've missed?