Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 1577 by [email protected]: fallback trigger key handling on ibus
side if panel service cannot handle it.
http://code.google.com/p/ibus/issues/detail?id=1577
Before ibus 1.5, ibus is taking care of the trigger key. While 1.5 leaves
that part to panel service, it breaks kimpanel and means I need to
reimplement everything in panel on my own side, which makes me feel very
bad.
Shouldn't there be a least compatible layer that if "panel service" cannot
handle this, and make ibus itself still handle the trigger key? Though It's
already too late to blame 1.5 internal change that already breaks code
outside ibus.
--------
Well, this report is valid or not depends on how ibus dev think about it.
But one of the purpose I report it here is to complain about the way that
ibus API goes to (I mean compatibility).
--
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
