That's because there are no constants for the majority of keys. Their
value depends on their location on the keyboard. For example, the
letter a on one keyboard layout may be the same place as the letter q
on another, but they will both have the same keycode.
For the letters and punctuation, you need to use something like
UCKeyTranslate() to translate them into strings.
CFStringRef CopyStringForKeyCode(UInt16 keyCode)
{
unsigned int i;
if (keyCode==0)
return NULL; // We don't want to scan the glyph table
with a zero keycode. The key with the zero keycode is 'a' on the
QWERTY layout. Use UCKeyTranslate() for other keys not in this table.
for (i=0;i<sizeof(kGlyphTable) / (sizeof(GlyphTable));i++)
{
if (kGlyphTable[i].keyCode == keyCode)
{
if (kGlyphTable[i].unicode)
{
CFStringRef string=CFStringCreateWithCharacters(NULL,
&(kGlyphTable[i].unicode), 1);
return string;
}
else if (kGlyphTable[i].keyString)
{
return CFRetain(kGlyphTable[i].keyString);
}
break;
}
}
return NULL;
}
Ack, at 7/13/06, Tom Harrington said:
Is there any sort of decoder information for the numbers returned by
NSEvent's -keyCode method? The docs just note that the "...value
returned is the same as the value returned in the kEventParamKeyCode
when using Carbon Events." But that doesn't seem to be documented or
decoded anywhere that I can find.
I can get codes for specific keys empirically by pressing them and
seeing what keyCode results, but I would have expected constants
somewhere.
--
Sincerely,
Rosyna Keller
Technical Support/Holy Knight/Always needs a hug
Unsanity: Unsane Tools for Insanely Great People
It's either this, or imagining Phil Schiller in a thong.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
