W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2008

Re: ISSUE-23 (Key Indentifier Case): Should Key Identifiers prioritize uppercase characters [DOM3 Events]

From: Andrew Cunningham <andrewc@vicnet.net.au>
Date: Mon, 30 Jun 2008 13:50:30 +1000
Message-ID: <48685806.8010406@vicnet.net.au>
To: Cameron McCormack <cam@mcc.id.au>


Cameron McCormack wrote:
>> At best you might be able to determine what keystrokes are used (maybe  
>> not always) and what characters are ultimately generated, although  
>> characters generated may not be in the same order as keystrokes that  
>> generate those characters.
>>     
>
> I think for these key identifier strings we shouldn’t be worrying about
> what character input is then generated and passed to the application,
> since that’s the job of TextEvent.
>
>   
I guess I'm not following this.

So you're just looking at the scan codes then of the keys being pressed?

if i press the q/Q key are you looking at a particular physical key key 
on the keyboard? i.e. ultimately at the scan codes or virtual key codes?

or are you looking at a higher level?

i.e. the q/Q key on a QWERTY keyboard is a different physical key than 
the q|Q key on a AZERTY keyboard.

So are you using a positional approach using the virtual keys or scan 
codes of the physical keyboard, or are you interpreting the keystroke at 
a higher level so that key interpretation is mnemonic, i.e. does it 
matter which key is typed? or is it the q-key independent of the 
physical position of the q|Q key on the keyboard?

Andrew

-- 
Andrew Cunningham
Vicnet Research and Development Coordinator
State Library of Victoria
328 Swanston Street
Melbourne VIC 3000

Ph: +61-3-8664-7430
Fax: +61-3-9639-2175

Email: andrewc@vicnet.net.au
Alt email: lang.support@gmail.com

http://home.vicnet.net.au/~andrewc/
http://www.openroad.net.au
http://www.vicnet.net.au
http://www.slv.vic.gov.au


Received on Monday, 30 June 2008 04:19:04 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:26 GMT