Branch: refs/heads/master
Home: https://github.com/ibus/ibus
Commit: 06e6abee9f221bdf7c277538ce136154465619d7
https://github.com/ibus/ibus/commit/06e6abee9f221bdf7c277538ce136154465619d7
Author: Daiki Ueno <[email protected]>
Date: 2011-04-05 (Tue, 05 Apr 2011)
Changed paths:
M bus/engineproxy.c
M bus/engineproxy.h
M bus/inputcontext.c
M client/gtk2/ibusimcontext.c
M configure.ac
M ibus/engine.py
M ibus/interface/iengine.py
M ibus/interface/iinputcontext.py
M src/ibusengine.c
M src/ibusengine.h
M src/ibusinputcontext.c
M src/ibusinputcontext.h
M src/ibusmarshalers.list
Log Message:
-----------
Support surrounding-text retrieval.
Unlike the GtkIMContext API, IBus automatically retrieves
surrounding-text when certain events occurred to the
client ("before filter_keypress", for example). This makes the
engine API simpler but causes periodical emission of D-Bus
signals for updating surrounding-text information, which is
unwanted for typical engines.
For this reason, the surrounding-text support is currently
disabled by default. To enable it, pass
--enable-surrounding-text to configure. Also, even
surrounding-text support is compiled in, IBus does not start
polling until an engine requests surrounding-text using
ibus_engine_get_surrounding_text(). To make the function work
for the first time, clients should retrieve
initial surrounding-text when the engine is enabled (see
ibus_im_context_focus_in() and
_ibus_context_enabled_cb() in client/gtk2/ibusimcontext.c).
BUG=Issue#778
TEST=manual
Review URL: http://codereview.appspot.com/4276082
Patch from Daiki Ueno <[email protected]>.
--
You received this message because you are subscribed to the Google
Groups "ibus-devel" group.
iBus project web page: http://code.google.com/p/ibus/
iBus dev group: http://groups.google.com/group/ibus-devel?hl=en
