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.
Works great, except in the case of pressing Up or Down on a Palm 5-way navigator equipped device (tested on my T|T and Z71). In this case, the 5-way vchrNavChange key event that is sent after the vchrPageUp/vchrPageDown key is treated by TxtGlueCharIsPrint() as true, and falls into my processing routine when it should have been left to the system. Why does TxtGlueCharIsPrint( vchrNavChange ) == true when it should be false? Is this a PalmSource PalmOS gluelib problem, or a PalmSG implementation problem? Who do I report this to? David Thacker -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
