GaryHT627
|
2010-01-16
, 00:22
|
Posts: 26 |
Thanked: 25 times |
Joined on Jan 2010
@ USA, Maine
|
#31
|
|
2010-01-16
, 00:56
|
Posts: 33 |
Thanked: 10 times |
Joined on Jan 2010
|
#32
|
|
2010-01-16
, 01:42
|
Posts: 33 |
Thanked: 10 times |
Joined on Jan 2010
|
#33
|
|
2010-01-16
, 04:01
|
Posts: 356 |
Thanked: 172 times |
Joined on Jan 2010
@ Canada
|
#34
|
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.
|
2010-01-16
, 15:23
|
Posts: 52 |
Thanked: 11 times |
Joined on Nov 2009
@ UK
|
#35
|
i just think butterfly should go to an iphone forum or at least a thread discussing iphone vs n900. there's plenty of them!
|
2010-01-17
, 11:34
|
Posts: 61 |
Thanked: 36 times |
Joined on Feb 2006
@ Harpenden
|
#36
|
|
2010-01-17
, 13:20
|
Posts: 33 |
Thanked: 10 times |
Joined on Jan 2010
|
#37
|
I switched on debug in iSync (launch it whilst holding down Shift and Option).
vCal to parse: BEGIN:VCALENDAR VERSION:1.0 TZ:+00 DAYLIGHT:TRUE;+01;20100328T020000;20101024T010000;GMT;BST BEGIN:VEVENT SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:= Test=20event UID:511 DTSTART:20100129T125000Z DTEND:20100129T135000Z ATTACH: SEQUENCE:0 LAST-MODIFIED:20100117T123018Z DCREATED:20100117T123006Z END:VEVENT END:VCALENDAR
vCal parsed: { RawProperties = ( { Name = UID; Value = <353131>; }, { Name = SEQUENCE; Value = <30>; }, { Name = "LAST-MODIFIED"; Value = <32303130 30313137 54313233 3031385a>; }, { Name = DCREATED; Value = <32303130 30313137 54313233 3030365a>; } ); "all day" = 0; "com.apple.syncservices.RecordEntityName" = "com.apple.calendars.Event"; "end date" = "2010-01-29 13:50:00 +0000"; "start date" = "2010-01-29 12:50:00 +0000"; summary = "Test event"; }
vCal to parse: BEGIN:VCALENDAR VERSION:1.0 TZ:+00 DAYLIGHT:TRUE;+01;20100328T020000;20101024T010000;GMT;BST BEGIN:VEVENT SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:= Testing=20alarms=20w/log UID:513 DTSTART:20100129T132000Z DTEND:20100129T142000Z ATTACH: SEQUENCE:0 LAST-MODIFIED:20100117T130040Z DCREATED:20100117T130040Z AALARM:20100129T130500 ;PT3M ; END:VEVENT END:VCALENDAR
Failed to parse vCal (1) near index 97: BEGIN:VEVENT SUMMARY;ENCODING=QUOTED-PRINTABLE;CHARSET=UTF-8:= Testing=20alarms=20w/log UID:513 DTSTART:20100129T132000Z DTEND:20100129T142000Z ATTACH: SEQUENCE:0 LAST-MODIFIED:20100117T130040Z DCREATED:20100117T130040Z AALARM:20100129T130500 ;PT3M ; END:VEVENT END:VCALENDAR
|
2010-01-17
, 13:41
|
Posts: 33 |
Thanked: 10 times |
Joined on Jan 2010
|
#38
|
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?
vCal generated: BEGIN:VCALENDAR VERSION:1.0 BEGIN:VEVENT DTSTART:20100130T140000Z DTEND:20100130T150000Z CLASS:PUBLIC AALARM:20100129T140000Z SUMMARY:Testing from iCal END:VEVENT END:VCALENDAR
|
2010-01-17
, 14:00
|
Posts: 33 |
Thanked: 10 times |
Joined on Jan 2010
|
#39
|
|
2010-01-17
, 14:02
|
Posts: 61 |
Thanked: 36 times |
Joined on Feb 2006
@ Harpenden
|
#40
|