Comment #5 on issue 1162 by anergy.25110321: ibus emits GdkEventKey.state with unused bits.
http://code.google.com/p/ibus/issues/detail?id=1162
Yes, it's the easiest way to change CLEAN macro of vimprobable to mask 1<<25 bit of GdkEventKey.state with GDK_ANY_OTHER_SUPPORT_MASKS. And on the other hand, the modification of ibus to fix this problem seems more difficult. Although, there are more applications using GdkEventKey.state without GDK_ANY_OTHER_SUPPORT_MASKS, such as surf:http://http://surf.suckless.org/ ,uzbl:http://www.uzbl.org/ , and so on. I don't know who must take care of GdkEventKey.state. It can be said that ibus should not give internal information in outgoing event, but also it can be said that gtk applications should mask the state correctly. I think GdkEventKey.state should be used only for representing which mod key is pressed. And the fixing ibus may suppress other underlying problem which is caused by this issue. Is there no way not to using GdkEventKey.state as the condition whether the event is handled by ibus?
-- 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
