I'm certainly no Text Manager expert (I probably don't even rate "novice!), but
looking at the TextMgr.h header, the solution I'd probably take is to call
TxtFindString, passing in a one-character string instead of the char that StrChr
takes.
Or I might continually call TxtGetNextChar and test the returned char. But I
think the former woud be easier and faster.
-- Keith
Paul Nevai <[EMAIL PROTECTED]> on 01/31/2001 05:04:11 AM
Please respond to "Palm Developer Forum" <[EMAIL PROTECTED]>
Sent by: Paul Nevai <[EMAIL PROTECTED]>
To: "Palm Developer Forum" <[EMAIL PROTECTED]>
cc: (Keith Rollin/US/PALM)
Subject: StrChr...
Please look at the code of StrChr () in StringMgr.c [I can't quote here]. It
seems to me that when it returns (Char *)str, it may not be the correct
location in a multi-byte environment.
What is the right way to do a StrChr () job in a possibly multi-byte
environment? Should I use StrChr () or a Text Manager function for that job
or should I create a custom routine? Best regards, Paul
--
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/
