On Sa, 2014-05-24 at 21:21 -0400, Dave Mielke wrote: > [quoted lines by Peter Maydell on 2014/05/25 at 01:04 +0100] > > >Why is this a problem only for the curses UI frontend, and not for > >any of the other UIs which might send key events? > > One reason is that most UIs send key events as they receive them from the > keyboard, one at a time, whereas the curses UI gets a single key event from > curses and then sends all of the scancodes which it takes to represent that > key. In other words, a single key event from curses could result in as many > as > 10 actual key events needing to be passed along - both the press and release > for the actual key plus up to four modifiers (shift, control, alt, altgr).
Tried to make the curses ui a bit more clever? You could try caching the modifier state, then send only the changes. That gets the number of events down to 6 max (4 to update modifier state, 2 for the actual key). Other question: has "git revert 2858ab09e6f708e381fc1a1cc87e747a690c4884" any effect? cheers, Gerd
