Why does the shortcut character (chrShortcutStroke) persist in a text field
if no text is entered after it?
In my application, if a user enters a shortcut character in a text field,
chrShortcutStroke is mapped to chrEndOfTransmissionBlock in Chars.h, which
is 0x17. My conduit gets 0x17 and it's XML parser chokes because it is not
in the iso-8859-1 character set.
For the short term, I'm just stripping out chrShortcutChar, but what would
be a more general solution? I see there are other "special characters" in
Chars.h:
// Special meanings given to characters by the PalmOS
#define chrOtaSecure chrDeviceControlFour // 0x0014
#define chrOta chrNegativeAcknowledge // 0x0015
#define chrCommandStroke chrSynchronousIdle // 0x0016
#define chrShortcutStroke chrEndOfTransmissionBlock // 0x0017
#define chrEllipsis chrCancel // 0x0018
#define chrNumericSpace chrEndOfMedium // 0x0019
#define chrLeftArrow chrFileSeparator // 0x001C
#define chrRightArrow chrGroupSeparator // 0x001D
#define chrUpArrow chrRecordSeparator // 0x001E
#define chrDownArrow chrUnitSeparator // 0x001F
Can any of these other characters be input into text fields by the user?
How can I force my app to only work with the Latin character set? Ideally,
if run on a Palm with a different encoding, it would pop up an error message
(future versions may support other encodings).
An alternative is to have my conduit run all the text through a filter which
enforces a particular character set.
Joseph Koral
[EMAIL PROTECTED]
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
