On Mo, 2011-06-20 at 15:03 +0100, Lukas Zeller wrote: > Hello, > > I don't see why it should work in the simple profile but not work in the > complex one. > > However, maybe this is a red herring and the problem lies in the > fReceivedFieldDefs (in TMimeDirItemType) flag. This is a per-type flag > which is set once a property list from devInf was parsed with > TMimeDirProfileHandler::analyzeCTCap().
That function is only called once during a sync session. The updated or added CtCap is inserted into TSyncSession::analyzeRemoteDevInf() by the checkRemoteSpecifics() call, which runs before the analyzeCTCap() call later in analyzeRemoteDevInf(). > Its effect is that when parsing a CTCap again (which is still > possible), the available status of the fields are NOT reset before > parsing the CTCap, such that possibly more fields get enabled, but > those that are already enabled from a previous CTCap scan remain > enabled. This is needed e.g. for combining vCalendar subtypes > VEVENT/VTODO. > > Could it be that the new OverrideDevInf somehow causes this flag to be > reset in an early stage, such that parsing the without X-AIM will > still result in AIM_HANDLE enabled, because it was set somehow > previously? So that doesn't seem to be it. I'm now looking at the actual parser code... gdb to the rescue. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ os-libsynthesis mailing list [email protected] http://lists.synthesis.ch/mailman/listinfo/os-libsynthesis
