[interfacekit] Re: input method extension
- From: "Jérôme Duval" <korli@xxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Thu, 26 Oct 2006 14:01:33 +0200
2006/10/25, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:
Hi there,
I've extended the input method mechanism a bit to allow for input
methods that don't cause a bottom-line window in case the current
target view isn't input method aware.
This works as following:
1) you add a boolean "be:inline_only"=true to all
B_INPUT_METHOD_EVENTs
2) in the final B_INPUT_METHOD_CHANGED event (the one that
confirms
the
"transaction"), you add a message in "be:translated". This message
will only be
used in case the current view does not understand input methods.
IOW it will
usually contain a B_KEY_DOWN message.
The input_server will then make sure that the target view gets what it
deserves :-)
I've implemented a visual feedback for dead keys this way. If you see
problems in this approach, or have a better idea, please notify me!
In any way, it shouldn't change previous behaviour for views that don't
support input methods.
Cool and impressive! :)
Are input methods correcly working with your fixes btw ? At a time there was
an opened bug with when switching focus windows.
Bye,
Jérôme
- Follow-Ups:
- [interfacekit] Re: input method extension
- From: Axel Dörfler
- References:
- [interfacekit] input method extension
- From: Axel Dörfler
Other related posts:
- » [interfacekit] input method extension
- » [interfacekit] Re: input method extension
- » [interfacekit] Re: input method extension
Hi there,
I've extended the input method mechanism a bit to allow for input
methods that don't cause a bottom-line window in case the current
target view isn't input method aware.
This works as following:
1) you add a boolean "be:inline_only"=true to all
B_INPUT_METHOD_EVENTs
2) in the final B_INPUT_METHOD_CHANGED event (the one that
confirms
the
"transaction"), you add a message in "be:translated". This messagewill only be
used in case the current view does not understand input methods.
IOW it will
usually contain a B_KEY_DOWN message.The input_server will then make sure that the target view gets what it deserves :-)
I've implemented a visual feedback for dead keys this way. If you see problems in this approach, or have a better idea, please notify me! In any way, it shouldn't change previous behaviour for views that don't support input methods.
- [interfacekit] Re: input method extension
- From: Axel Dörfler
- [interfacekit] input method extension
- From: Axel Dörfler