Re: Handle ^ and ¨ in a field

[Devin Asay]

On Apr 7, 2008, at 1:12 PM, Ken Ray wrote:
> On Mon, 7 Apr 2008 13:14:35 +0200, Björnke von Gierke wrote:
>
>>
>> On 7 Apr 2008, at 12:17, Jean-Pierre wrote:
>>> Hello,
>>>
>>> I want to handle caracter one by one in a field.
>>>
>>> If I use keyUp : caracter was missing when user type rapidly.
>>>
>>> If I use keyDown : accentued caracter such â,ê,ï was missing.
>>>
>>> What can I do ?
>>
>>
>> Revs international char support in keyUp/down is... sub optimal. I
>> suggest to use rawkeydown or rawkeyup until they update the other
>> ones, but of course that'll be a lot of additional work for you.
>
> And it also doesn't work properly (at least on a Mac). If you type
> option-u, then "o" in order to get an "o" with an umlaut, you (a)  
> don't
> get any rawKeyDown message when you type option-u, (b) when you type
> the "o" you get the o with the umlaut in the field you're typing in,
> but the rawKeyUp message returns "117" for the "u" you typed, and then
> another rawKeyUp of "111" for the "o", and finally (c) you can't
> prevent the user from entering accented characters into a field -
> normally if you trap rawKeyDown or rawKeyUp and don't pass it, you
> won't get anything entered in the field. But accented characters  
> bypass
> this and display automatically.
>
> I just entered this into RQCC:
> http://quality.runrev.com/qacenter/show_bug.cgi?id=6347

This is probably related to this one:

http://quality.runrev.com/qacenter/show_bug.cgi?id=3537

Devin

Devin Asay
Humanities Technology and Research Support Center
Brigham Young University