On Tue, Mar 19, 2013 at 11:01 AM, Friar <[email protected]> wrote: > Please also consider the case of video games that are running in > non-full-screen mode that don't WANT key auto-repeat. They should have a > way to turn off repeated notifications. Having to wade through a ton of > auto-repeated keyboard events to find the actual up/down signals is likely > to cause some input lag and even a few milliseconds can affect performance. > Clients shouldn't be forced to create crazy outside connections directly to > input devices to get primitive input handling.
I am just wondering if those clients also don't want auto-repeat for text input. If there is a way to turn off auto-repeat for a client, should that also turn off the auto-repeat when the input method grab the keyboard from the client? > > --Brenden > > > On Mon, Mar 18, 2013 at 4:59 PM, Bill Spitzak <[email protected]> wrote: >> >> For text, I would expect the input method is going to do the key-repeat. I >> can't see any way around that. So for the most common use of key repeat it >> is going to be handled outside the client, and users will see a held-down >> letter repeatedly insert at the same rate in all clients (or at least all >> clients that also correctly work with input methods). >> >> If the user holds down a function key, imho it would be nice if the >> compositor did the repeat. The repeat events just have to be clearly >> identified so if a client really wants to do it's own rate, all it has to do >> is ignore the repeat events. This does avoid annoying problems where clients >> on the same display disagree, and it >> >> For the same reasons, I also feel that holding the mouse button down >> should "repeat", and holding the mouse still should produce "hover events" >> (for highlight and popping up tooltips), mouse clicks should be marked with >> whether the compositor thinks they are "double", and dragging the mouse >> should produce a "this is a real drag" event when the compositor thinks it >> moves far enough that the user really is trying to move something. All these >> would get rid of the incredibly annoying mismatch between clients that >> current X and Windows programs have. Again the events just have to be >> clearly marked so it is easy for a client to ignore them and do it's own >> processing in cases it wants to be different. >> >> _______________________________________________ >> wayland-devel mailing list >> [email protected] >> http://lists.freedesktop.org/mailman/listinfo/wayland-devel > > > > _______________________________________________ > wayland-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/wayland-devel > _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
