Codejock Developer Community : Change to recurring (AKA Yet another bug fix)

Change to recurring (AKA Yet another bug fix) : 11.2.0 is fixed, thanks a bunch. ...

Fri, 19 Oct 2007 18:57:54 +0000

Author: JohnCrenshaw
Subject: 7241
Posted: 19 October 2007 at 6:57pm

11.2.0 is fixed, thanks a bunch.

Change to recurring (AKA Yet another bug fix) : Just installed 11.1.3 and this...

Fri, 24 Aug 2007 16:17:13 +0000

Author: JohnCrenshaw
Subject: 7241
Posted: 24 August 2007 at 4:17pm

Just installed 11.1.3 and this still hasn't been fixed, just want to make sure that this gets into the next build.

Change to recurring (AKA Yet another bug fix) : This should only an issue when...

Fri, 25 May 2007 13:15:36 +0000

Author: JohnCrenshaw
Subject: 7241
Posted: 25 May 2007 at 1:15pm

This should only an issue when using the MAPI data provider (I didn't test the other, so I can't be 100% sure.)

In xtpcalendarmapidataprovider.cpp at line 3542 we are inside the MAPI callback, dealing with the fact that the event changed, and updating the cache. On this line, there is a silly mistake.

ptrEvent2->SetRecurrencePatternID(dwPatternID);

the pattern ID was just grabbed from another event pointer, and now it is being coppied over to this one. This is fine, except that in this case, the old event HAD no pattern ID, and the new one does. This causes the code inside _AddRPatternWithExceptions (called by ChangeEvent which is called on the next line) to fail when it assumes that we DO have an ID. The fix is fairly basic.

if (dwPatternID != XTP_CALENDAR_UNKNOWN_RECURRENCE_PATTERN_ID){
    ptrEvent2->SetRecurrencePatternID(dwPatternID);
}