On Thu, 8 Jun 2017, Owen Smith wrote: > Mouse events are only delivered to the first handler in the chain. > Activating the xenfb mouse event handler so that mouse events can > be passed over the shared ring protocol. > Note: The keyboard handler is activated internally by the add > call.
I am not sure I follow: why do we need this now? How is it working today? > Signed-off-by: Owen Smith <owen.sm...@citrix.com> > --- > hw/display/xenfb.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/hw/display/xenfb.c b/hw/display/xenfb.c > index 2ebc81b..b0a5726 100644 > --- a/hw/display/xenfb.c > +++ b/hw/display/xenfb.c > @@ -385,6 +385,7 @@ static void input_connected(struct XenDevice *xendev) > in->qmouse = qemu_add_mouse_event_handler(xenfb_mouse_event, in, > in->abs_pointer_wanted, > "Xen PVFB Mouse"); > + qemu_activate_mouse_event_handler(in->qmouse); > } > > static void input_disconnect(struct XenDevice *xendev) > -- > 2.1.4 >
