Comment #5 on issue 1419 by [email protected]:
Were "enabled"/"disabled" signals and enable()/disable() methods
accidentally removed?
http://code.google.com/p/ibus/issues/detail?id=1419
Yes, "ic" means input context, but I said nothing about the input mode, and
cannot understand why you mentioned the input mode and the global input
mode. "enable" and "disable" merely mean "use IM engine" and "don't use IM
engine", respectively. In latest IBus, "don't use IM engine" is same
as "use xkb engine". (In the older IBus, "don't use IM engine" is "disable
IM engine".)
Do you mean ibus-mode changes the default trigger key from Control+Space
to other keys?
If yes, probably I don't think it's a good idea but I'd suggest to use
ibus-setup to customize the trigger key.
I'd like to suggest the default Control+Space is owned by input methods
and users still customize it.
Disagreed. Emacs users want to unset the trigger key only for Emacs. In
the other applications, they still use Ctrl+SPC to toggle IM. How can we
change the key binding for each application in ibus-setup??? Also, even if
such "per-application" setting can be done, IPC cannot be reduced.
You didn't say why the latest IBus doesn't provide the signal to indicate
that IM engine was changed. Without the signal, ibus-mode have to watch
periodically which engine is currently used. That causes much IPC and
waste the CPU time. I think that's a nightmare!
--
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
