On Mon, 12 Jun 2006 01:48:31 -0400,
B.J. Buchalter (email@hidden) wrote:
>So, I can't use kEventTextDidChange cause I am targeting 10.3 too.
>
>I have found that I need to do the following (and it appears to work OK):
>
>For catching the text updates:
>
>Add a { kEventClassTextInput, kEventTextInputUnicodeForKeyEvent} on the
>text control. In this handler, I call CallNextEventHandler(), and then
>notify my clients afterwards.
That approach will work with most western keyboards, but it may
fail to detect text entered by input methods such as Kotoeri
(the default input method for Japanese). In order to catch
characters entered via input methods, you may want to add a similar
handler for {kEventClassTextInput, kEventTextInputUpdateActiveInputArea},
and notify your clients if the kEventParamTextInputSendFixLen parameter
is non-zero.
-- marco
--
It's not the data universe only, it's human conversation.
They want to turn it into a one-way flow that they have entirely
monetized. I look at the collective human mind as a kind of
ecosystem. They want to clear cut it. They want to go into the
rainforest of human thought and mow the thing down.
_______________________________________________
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
