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: Mon, 01 Aug 2005 00:27:47 -0400
Thanks. I'll check it out further.
> 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.
_______________________________________________
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