I found the real reason, which I think is a bug introduced in
/branches/sogo/libmapi/IMAPIProp.c @ 2798, but which only surfaces if
MAPI_PROPS_SKIP_NAMEDID_CHECK is not used.
Basically, if any named properties are used and skipping is not in
effect, then the "named" boolean is set. This is used t
Never mind...
(gdb) p/x 2182480130
$116 = 0x82160102
(gdb) p/x -2112487166
$117 = 0x82160102
___
devel mailing list
devel@lists.openchange.org
http://mailman.openchange.org/listinfo/devel
So, watch what happens as I step through the loop in
mapi_nameid_unmap_SPropTagArray, when called from inside GetProps...
(gdb) n
742
SPropTagArray->aulPropTag[mapi_nameid->entries[i].position] = (enum
MAPITAGS) mapi_nameid->entries[i].proptag;
(gdb)
740 for (i = 0; i < mapi_nameid->co
Hi,
I think there is an issue in automatically mapping and unmapping
PidLidXxx items.
At present, my code is blissfully unaware of the special handling of
PidLixXxx items. I simply ask for PidLidAppointmentRecur, call
GetProps (without asking for the named id skipping), and look at the
returned v
