I'm trying to map a keyboard scancode to a displayable string on OSX.
I found the technique here (Convert key code into key equivalent string) which works for all the normal ascii letters and numbers, but for all the other keys i.e. directional arrows, return etc I just get non printable characters back. What strikes me as odd is that the UCKeyTranslate function used takes an array of UniChars, but only ever returns a single character.
What I'm looking for is something akin to the DirectInput DIPROP_KEYNAME functionality found on windows.
I'm struggling to accept that in todays modern operating systems I'm going to have to resort to hardcoding string values for each of the "unsupported" keys.
Is there something I'm missing?