Thank you Dethe, I'll look into this. On 28-Mar-06, at 1:35 PM, Dethe Elza wrote:
> Well, I'm trying real hard *not* to look for control codes in > keypress, but when I press F5 then keypress is firing and the > evt.key().string is "t", while the evt.key().code is 116. If I press > the "t" key I get the exact same results. Now, if I dive down to the > native event, the evt.event().keyCode is 0 for "t" and the > evt.event().charCode is 0 for F5, but that's the only way I can tell > them apart right now. I'm trying to filter non-printing keys out, so > I need some way to detect F5 in keypress so I can ignore it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit -~----------~----~----~----~------~----~------~--~---
