>I'm a bit confused about this one... it returns true for vchrPrevField and
>false for vchrNextField. under 4.0dr5.
That's because the character code is being used to index into an
array of 256 attributes (at least on a Latin device), so character
codes > 256 will return back garbage results.
>I know the old IsPrint function only handled ascii (i.e. <255), but this
>function accepts a WChar and the doc says "Returns true if the character is
>not a control or virtual character, false otherwise."
The documentation is wrong. TxtCharIsPrint, along with all of the
other character attribute calls, assumes that you are passing it a
standard (not virtual) character code. Even though currently the
virtual character codes are in a range that's distinct from standard
character codes, this won't be the case in the future.
Note that if you tried calling TxtCharIsPrint(virtual char) on a
debug ROM, you'd get a fatal alert that says "Invalid char passed to
TxtCharAttr".
-- Ken
Ken Krugler
TransPac Software, Inc.
<http://www.transpac.com>
+1 530-470-9200
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
