Comment #5 on issue 1184 by takao.fujiwara1: ibus loses timestamps for key
events
http://code.google.com/p/ibus/issues/detail?id=1184
Revised the patch:
https://github.com/fujiwarat/ibus/commit/5cb36a3ab53038cf0723e7a37c2539c638403324
Thanks for the reviews and suggestions.
I took the first approach again to save the latest time value in
IbusIMContext.
We have one problem. If we would pass the time value to IBus DBus
functions, probably many functions would need to be updated with the time
argument in gtk-client and IM engines. However probably the time value
would not be so useful meaning for each IM engine.
So probably we would not like to pass the time value at the moment and
saving the latest time could be a solution.
On the other hand, we thought an idea to use the diff value.
In the first filter_keypress function, we take diff = - event->time +
_ibus_get_time_in_millis().
And we assign the time = ibus_get_time_in_millis() - diff before
gdk_event_put() is called.
Probably this idea also would not work in some X servers because some Xorg
could use clock_gettime() and others could use gettimeofday() and the
generated 'diff' value would be different in each X server and remote/local
X server.
--
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
