![]() |
Re: iSync and Mac support with maemo 5
Quote:
|
Re: iSync and Mac support with maemo 5
Well you can always load the plugin and just choose to synchronise a single group of contacts from the address book (maybe make a test group) to try it out. I have synchronised all of my contacts using my plugin and it works perfect :)
If not, stay tuned to this thread and hopefully we will have it all sorted soon. |
Re: iSync and Mac support with maemo 5
Syncing events with alarms from iCal to N900 now definitely works as expected but when they are created in iCal they must have the alarm type set to "Message with Sound". From what I can tell any other alarm type doesn't work.
Basically all that is missing now is, events created on the N900 with alarms, being imported from N900 to iCal. |
Re: iSync and Mac support with maemo 5
Quote:
It also didn't display any kind of notification today, which it should have. |
Re: iSync and Mac support with maemo 5
Quote:
I have been reading this thread with interest, as I never thought it would be possible to sync my iCal |
Re: iSync and Mac support with maemo 5
The only real difference I can see between our plugins is that you explicitly name the device SyncML Databases, but I use "No target database names in Server Alert" (whatever that means!) It doesn't seem to make any operation difference though.
I switched on debug in iSync (launch it whilst holding down Shift and Option). It generates reams of data in a log file (2Mb per sync), but searching it for any details of the N900 created event turned up nothing. It may be a problem on the N900 where it isn't exposing the event over SyncML for whatever reason, rather than a fault of the plugin or iSync. |
Re: iSync and Mac support with maemo 5
Quote:
I set up an event on the N900 without an alarm then synced, then repeated it with an event that had an alarm. There is as you say a lot of info in that log file but the following snippets I think is where the issue is. Event without alarm log Code:
vCal to parse: Code:
vCal parsed: Code:
vCal to parse: Code:
Failed to parse vCal (1) near index 97: BEGIN:VEVENT So... I guess we have to work out exactly what "Failed to parse vCal (1) near index 97" means? Well.. I know what it means, it failed! but where that problem is coming from.. iCal or N900? The formatting of the AALARM property? on different lines like that? Any ideas? |
Re: iSync and Mac support with maemo 5
Quote:
Code:
vCal generated: |
Re: iSync and Mac support with maemo 5
[QUOTE=3quid;478038]
The way I see it is that we dont need the ;PT3M; part of the AALARM that is coming from the N900. iCal, when sending, formats the AALARMS like this: AALARM:20100129T140000Z Broken down into AALARM - Alarm with message and sound Year - 2010 Month - 01 Day - 29 T - is to say the following is a time entry Time of alarm - 1400 00 (2pm and zero seconds) Z - I dont know what this Z means yet In the alarm event coming from the N900 it states AALARM:20100129T130500 ;PT3M ; So again it is broken into AALARM - Alarm with message and sound Year - 2010 Month - 01 Day - 29 T - is to say the following is a time entry Time of alarm - 1305 00 (1.50pm and zero seconds) [The alarm was set for 15 mins before the event which was at 13:20 so thats correct] ;PT3M - This according to here should mean that the alarm has a P (Snooze value) but that is blank. Then a T (Time) which is 3M (3 Minutes... why!?) So it is possible that if we could somehow swap the ;PT3M; for a Z it would work? :eek: |
Re: iSync and Mac support with maemo 5
Z is the timezone indicator.
I need to read the vCard spec I think. |
All times are GMT. The time now is 03:35. |
vBulletin® Version 3.8.8