Re: XInput2 by default in 3.0?
- From: Matthias Clasen <matthias clasen gmail com>
- To: Carlos Garnacho <carlosg gnome org>
- Cc: gtk-devel-list gnome org
- Subject: Re: XInput2 by default in 3.0?
- Date: Tue, 14 Dec 2010 14:18:34 -0500
On Tue, Dec 14, 2010 at 8:31 AM, Carlos Garnacho <carlosg gnome org> wrote:
> Hi!,
>
> I've been wanting to raise this topic for some time. The patch
> (attached) is simple, it basically will enable the XInput2
> GdkDeviceManager by default, unless gdk_disable_multidevice() is called.
>
> Even if the change looks intricated, the only new code that'd get
> exercised lies in gdk/x11/gdkdevice(manager)-xi2.c, and trying out 95%
> of that code is as easy as opening some test, typing something, and
> opening/closing a menu.
>
> As things are now, GTK+ behaves reasonably well by default with multiple
> device pairs, even though no widgets take advantage of it directly yet,
> enter/leave events would be compressed into a single pair if multiple
> pointers enter say a button. In short, how current unmodified GTK (and
> apps relying on core events) behave with multiple pointers now. GTK
> would obviously work as well under a single mouse/keyboard pair.
After rummaging around in the X backend in recent days, I also get the
impression that the xi2 implementation is actually more complete than
the xi one...
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]