brendan mccloskey

let me state straight away that this is not a Max-specific question. But I have been polling the relevant forum for answers with no joy. Ok, we all good?

Using 'some other program' to detect the ASCII code of key presses (within Ubuntu), I run the helpfile for "KeyState", and when I press spacebar, "32" is output to the debug window, and the numbers 0~9 generate the expected numbers; so all is good. But then when I implement the KeyState function within my code, asking it to look for ASCII 32, 32 becomes the letter "o" (which should be 111?). And even weirder, tab = 65239. WTAF?

Feel free to kick me off this forum, or say RTF-ASCII-M

Hi
let me state straight away that this is not a Max-specific question. But I have been polling the relevant forum for answers with no joy. Ok, we all good?

asciiunicode-ninja-needed

Anyone? I know this isn't a software- or OS-specific question, just can't understand why 32="o" and 65239=tab?? All the other keycodes are similarly bizarre.

ascii/unicode ninja needed