Comment #2 on issue 1184 by [email protected]: ibus loses timestamps for key events
http://code.google.com/p/ibus/issues/detail?id=1184
* The approach of storing a timestamp locally is better than nothing. It won't get the timestamps exactly right when multiple keystrokes are typed in quick succession. It's not as good as sending the timestamps along with the event.
* I don't think the XSERVER_TIME_IS_LATER check in your patch is needed, though it generally won't hurt anything. It is a problem if an app doesn't get any key events for around ~20 days since then the check won't be accurate.
* Your patch only handles the case where events are snooped, but this can be disabled by environment variable, and some apps (in particular the GNOME 3 shell) will hide key events from the snooper even if the environment variable isn't set.
-- 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
