realbasic-nug
[Top] [All Lists]

Re: Workarounds for Keyboard.KeyName?

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: Workarounds for Keyboard.KeyName?
From: Frank Condello <developer at chaoticbox dot com>
Date: Wed, 30 Apr 2008 14:53:37 -0400
Authentication-results: mx.google.com; spf=pass (google.com: domain of realbasic-nug-bounces at lists dot realsoftware dot com designates 66.116.103.65 as permitted sender) smtp dot mail=realbasic-nug-bounces at lists dot realsoftware dot com
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <fed2e2560804301036q72c8979n50db0f5dbf05ab3e at mail dot gmail dot com>
On 30-Apr-08, at 1:36 PM, Dennis Birch wrote:

> The built-in Keyboard.KeyName function in RB does not work properly
> for some keys on my keyboard in Mac OS X 10.5.2. I believe this is a
> known issue, and so I'm wondering if there is a known workaround?

I sent in a couple bug reports regarding this and re-submitted them  
to Fogbugz. One bug is that it sometimes returns the wrong key name  
on QWERTY layouts (e.g. for the Tilde/Grave key) and another huge bug  
is that it always returns QWERTY names regardless of the actual layout.

The only "workaround" is to write all new code that handles this and  
ignore the built-in function. Unfortunately as far as I can tell  
there is no way to do this on Mac OS X without using deprecated  
functions. I have some declares buried away that use old-world  
functions (basically only works for English layouts) but I haven't  
gotten around to updating things to work with the newer unicode APIs.  
BTW: There are also bugs on Windows for non US-English layouts - but  
I'll let someone else worry about those...

Frank.
<http://developer.chaoticbox.com/blog/>


_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>