> On debug ROMs, if you pass virtual characters to TxtCharAttr, you'll
> get a non-fatal alert. On release ROMs, it will blindly use the
> character code value as an index into an array of attributes. Since
> this array only contains 256 elements, a virtual character winds up
> returning random dat
> >Why does TxtGlueCharIsPrint( vchrNavChange ) == true when it should be
>false?
I think you need to filter your processing to throw out any keys with the
command flag set before you try to process them as printable or not. No
> printing character will ever have that set, AFAIK.
Ben, as usu
> >Why does TxtGlueCharIsPrint( vchrNavChange ) == true when it should be
> >false?
>
> I think you need to filter your processing to throw out any keys with the
> command flag set before you try to process them as printable or not. No
> printing character will ever have that set, AFAIK.
>
Hi Ben
At 02:47 PM 6/17/2003, David Thacker wrote:
Greetings,
I use the gluelib functions TxtGlueCharIsPrint() and/or TxtGlueCharIsGraph()
in a routine that processes incoming keystrokes. If TxtGlueCharIsPrint(
pEvent->data.keyDown.chr ) returns false, then I just ignore the key and let
the system have
Greetings,
I use the gluelib functions TxtGlueCharIsPrint() and/or TxtGlueCharIsGraph()
in a routine that processes incoming keystrokes. If TxtGlueCharIsPrint(
pEvent->data.keyDown.chr ) returns false, then I just ignore the key and let
the system have it, otherwise I do stuff with the key.
Work
