Re: Bugs Involving Input Components Still Open in Radar
Re: Bugs Involving Input Components Still Open in Radar
- Subject: Re: Bugs Involving Input Components Still Open in Radar
- From: Maurice Volaski <email@hidden>
- Date: Thu, 28 Jul 2005 01:35:42 -0400
>> 3528513 : Input Method Always Supersede Keyboard Layouts
>> Input methods are treated by the OS as being equivalent to a keyboard
>> layout. That is, you can either choose a keyboard layout OR an
>> input method.
>> There is no way to have an input method act on the roman script
>> system and
>> permit the user to still be able to choose one of its keyboard
>> layouts.
>
> According to comments in the bug, this requires new API to work
> properly, and the API will be introduced in Leopard.
Cool.
>> 3753446: Text service components cannot backspace in Cocoa apps
>> Text service components can intercept keyboard events and modify
>> them or
>> post additional events including backspace to delete previously
>> typed text.
>> However, the backspace is ignored by Cocoa applications.
>
> This is assigned to a Cocoa engineer for investigation. Is this
> functionality crucial to your input method? The bug might get
> investigated sooner if you can explain in the bug why it's important
> for it to be fixed.
I have appended to the bug...
If the user types "teh" and I want fix it on the fly and retype "the", I
don't want the user to have to fix text. Therefore, I need to be able to
delete "teh" and type out "the".
In Classic, it was trivial to patch OSEventAvail and GetOSEvent to do this.
I just feed the application backspace keydowns until "teh" was deleted and
then feed it "the".
OS X has made this a garguantuan task. The most serious problem (this bug)
is that posting backspace keydowns in an Cocoa app from inside a text
service component is ignored.
I have tried other methods such as using the event monitor and posting
events through AXUIElementPostKeyboardEvent but that doesn't work because
of radar bug 4107468.
Even patching low-level event routines doesn't work because it appears that
_DPSNextEvent dispatches some keydowns directly into Cocoa apps.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden