Hi Alexey,
Even when we enable the "inline input for non-latin text" preference, it
doesn't seem to make a difference. It still shows up the floating window for
text input. I was wondering what this option really means.
Does this mean we can not get inline input to work using the
SendTextInputEvent() function ?
Thanks
Ajay
-----Original Message-----
From: Alexey Proskuryakov [mailto:email@hidden]
Sent: Monday, June 05, 2006 4:03 AM
To: Ajay Chitturi; email@hidden
Subject: Re: input method without floating window
On 29.05.2006 13:06, "Ajay Chitturi" <email@hidden> wrote:
> The text service component API is a good fit but our
> primary requirement is to support Adobe applications like InDesign,
Photoshop,
> etc and they don¹t support inline input so we get a floating window for
text
> input.
This doesn't really change the situation, but InDesign actually supports
inline input - it just needs to be enabled in application preferences.
> Users don¹t like the floating window it requires the user to concentrate
on
> two places in the window and slows down text input a lot. The main thing I
am
> looking for is if there is some other way I can send the characters to the
> application (in the form of keyboard events or some other way) so that the
> floating window can be avoided.
To send text input directly to the application, skipping the inline input
area or the floating window, you can use kEventTextInputUnicodeText event,
rather than kEventTextInputUpdateActiveInputArea (or just always mark the
text as "fixed" with the latter event). To check if TSM will use a floating
window for active text, use TSMGetDocumentProperty() with
kTSMDocumentUseFloatingWindowPropertyTag.
> A brief description of the script : The script essentially is a bunch of
> ligatures. So, the user experience we want to enable would be something
like
> this: Say the user types ³f², we show ³f². When the user types ³i² after
the
> f, we automatically change this to the ³fi² ligature.
For English, ligatures like "fi" are normally handled by the text layout
engine, and not the input metod. However, Korean seems similar, and Apple's
Hangul input method apparently works as you describe, producing precomposed
syllables. Hangul IM does show a floating palette for applications that do
not support inline input.
- WBR, Alexey Proskuryakov
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/carbon-dev/email@hidden
This email sent to email@hidden
