Hmm, OK. I guess there's no harm in leaving in the KCHR handling code. I
was hoping to simplify things (this routine is already big and yucky)
but I guess that's just not in the cards. Nothing about this whole
hotkey ordeal has been simple!
Ken Thomases wrote:
On Apr 17, 2008, at 11:38 AM, John Stiles wrote:
Quick question: in Leopard, are there any keyboards left which don't
have a uchr?
I found some sample code which includes a fallback case for if no
'uchr' resource is found (it uses plain KeyTranslate in this case)
and I'm wondering whether this is still relevant in the
Leopard-and-above timeframe.
All of the keyboard layouts that Apple ships provide uchr data.
However, there's nothing stopping users from installing and using
third-party keyboard layouts which don't. Many of those will be users
who originally installed the non-uchr keyboard layout in Tiger and
then upgraded to Leopard; the layout just comes along for the ride.
This is not a hypothetical. It has been a problem we've seen with our
product.
Cheers,
Ken
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
