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: Eric Schlegel <email@hidden>
- Date: Thu, 28 Jul 2005 10:36:41 -0700
On Jul 27, 2005, at 10:35 PM, Maurice Volaski wrote:
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".
I asked the Text Services Manager engineer about this, and he had the
following suggestion:
this looks like an ideal candidate for the TSMDocumentAccess event
suite.
If the TSMDocument (associated with the text field that currently
has focus) supports kTSMDocumentSupportDocumentAccessPropertyTag
(which it will for Cocoa), the input method can query part/all of
the text field using a CFString-like interface.
So after identifying the offending text via some combo of:
kEventTSMDocumentAccessGetSelectedRange
kEventTSMDocumentAccessGetCharacters
kEventTSMDocumentAccessGetLength
Once you've identified the offending text range, send an
UpdateActiveInputArea (auto-confirming) that specifies the
kEventParamTextInputSendReplaceRange param.
Hope this helps,
Michael
Perhaps you could try this and then you wouldn't have to feed
backspaces into the event stream to accomplish your auto-replace.
-eric
_______________________________________________
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