The current AddressBook application ignores these 8 bits.
0xd9 and 0x15 are just garbage bits left in there by
various manipulations.
I would put in 0x00 if I created the record, else
leave in whatever might have been there if I was editing
someone else's record.
-robert mckenzie
<[EMAIL PROTECTED]>
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Richard
Burmeister
Sent: Thursday, July 27, 2000 6:25 PM
To: Palm Developer Forum
Subject: AddressDB format -- 2nd attempt
Hello everyone. I received no responses for the last question, so here it
is again in a more compact format:
The AddrOptionsType defines bitfields that are used to control how phone
numbers are displayed in the Address Book. One of the fields, reserved, is
8 bits; the other 6 fields are all 4 bits.
When writing a record to the AddressDB, I would expect the reserved field to
always be 0x00. That's what the Address Book source code appears to use.
However, in testing with POSE and on my Vx, I have seen 0xD9, 0x00, and 0x15
in the reserved field. Does anybody know what these numbers mean? Is it
safe to just put 0x00 there when I create an address book record? Isn't
0x00 what's supposed to be there? If so, then it appears that there is a
bug somewhere in either the AddressBook itself or in its sync dll. If 0x00
isn't always supposed to be there, then I need to know what else should go
there.
Thanks for any info from anyone who knows about the AddressDB structure.
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
