Axis events to keyboard focus (Re: Input and games.)

Peter Hutterer peter.hutterer at who-t.net
Wed May 8 23:19:53 PDT 2013


On Mon, May 06, 2013 at 08:06:35PM -0500, Vincent Povirk wrote:
> > Windows used to do this and it is completely nuts. They fixed it in recent versions
> 
> I don't know what version of Windows you're using, but I can still
> observe this behavior in the Windows 8 file dialogs. I wrote a program
> to work around it: https://github.com/madewokherd/xscrollwheel
> 
> Some toolkits on Windows, like gtk, direct scroll wheel input based on
> cursor position, but they're not really using the native windowing
> system for their widgets. The upshot of this is that in gtk on Windows
> you can only scroll if your top-level window is focused AND your
> cursor is on something scrollable.
> 
> I don't think it makes sense to send a scroll wheel event to a window
> that's not beneath the cursor [...]

it does/may to the user if the scroll wheel is located on the physical
keyboard.

Cheers,
   Peter

> A compositor could just drop events that aren't over a focused window,
> and it would solve Todd's problem, unless he's also expecting to be
> able to scroll things without hovering over them.


More information about the wayland-devel mailing list