Re: [PATCH] xwayland-input: Remove our XYToWindow handler

2015-09-18 Thread Olivier Fourdan
Hi Jasper, Daniel, On 06/04/15 18:52, Daniel Stone wrote: On 23 February 2015 at 15:40, Daniel Stone wrote: On 21 February 2015 at 19:53, Jasper St. Pierre wrote: [...] Signed-off-by: Jasper St. Pierre Acked-by: Daniel Stone Keith, please pick this up, with tags from Olivier and mysel

Re: [PATCH] xwayland-input: Remove our XYToWindow handler

2015-04-06 Thread Daniel Stone
On 23 February 2015 at 15:40, Daniel Stone wrote: > On 21 February 2015 at 19:53, Jasper St. Pierre wrote: >> This was built as a hack for simple Wayland compositors like Weston >> which were lazy and didn't want to configure windows server-side when >> moved. >> >> Since comboboxes and menus are

Re: [PATCH] xwayland-input: Remove our XYToWindow handler

2015-02-23 Thread Daniel Stone
On 21 February 2015 at 19:53, Jasper St. Pierre wrote: > This was built as a hack for simple Wayland compositors like Weston > which were lazy and didn't want to configure windows server-side when > moved. > > Since comboboxes and menus are separate toplevel O-R windows, this hack > breaks input a

Re: [PATCH] xwayland-input: Remove our XYToWindow handler

2015-02-23 Thread Olivier Fourdan
On 21/02/15 20:53, Jasper St. Pierre wrote: This was built as a hack for simple Wayland compositors like Weston which were lazy and didn't want to configure windows server-side when moved. Since comboboxes and menus are separate toplevel O-R windows, this hack breaks input as it needs to be trac

[PATCH] xwayland-input: Remove our XYToWindow handler

2015-02-21 Thread Jasper St. Pierre
This was built as a hack for simple Wayland compositors like Weston which were lazy and didn't want to configure windows server-side when moved. Since comboboxes and menus are separate toplevel O-R windows, this hack breaks input as it needs to be traced normally, not simply sent to the focused wi