On Thu, Sep 27, 2012 at 11:32:48AM +0200, Olivier Fourdan wrote:
> Hi all,
>
> We have been discussing the need for an OSD window for some time.
>
> For GNOME, I made a simple implementation (see bug 679062 [1]) which
> seems to works quite well, but could be greatly improved with a more
> accura
On Fri, Sep 28, 2012 at 01:25:39PM +0200, Olivier Fourdan wrote:
> Hi Jason,
>
> Jason Gerecke said the following on 09/28/2012 12:19 AM:
> >On Thu, Sep 27, 2012 at 2:32 AM, Olivier Fourdan wrote:
> >>[...]
> >>
> >>Question:
> >>
> >>* Does any of the above makes sense? ;-)
> >Seems logical enou
On Sat, Sep 29, 2012 at 6:58 PM, Jason Gerecke wrote:
> This set of patches adds multitouch support to the driver. The new
> API made available in XI2.2 is used to report the location of all
> contacts, allowing applications to work with the touch points themselves.
> This is added as a new gestur
On Sat, Sep 29, 2012 at 6:58 PM, Jason Gerecke wrote:
> At the moment, disabling gestures disables *all* gestures. That includes
> the core "tap to click" gesture (and slightly-less-core "tap and hold to
> drag"). This patch changes the behavior of the driver to always allow
> single finger gestur
On Tue, Oct 2, 2012 at 2:53 PM, Jason Gerecke wrote:
> The prerequisite check in wcmUpdateSerial is incorrect. If the tool ID
> changes, the property reflecting it will not be updated unless/until the
> serial number also changes. The check is updated to reflect this.
>
> Additionally, the prerequ
The prerequisite check in wcmUpdateSerial is incorrect. If the tool ID
changes, the property reflecting it will not be updated unless/until the
serial number also changes. The check is updated to reflect this.
Additionally, the prerequesite check at one of its callsites is removed
since the functi
On Tue, Oct 2, 2012 at 8:09 AM, Olivier Fourdan wrote:
> The following two patches is an attempt to implement the status LED logic
> into libwacom.
>
> The logic was discussed very recently in this thread:
>http://sourceforge.net/mailarchive/message.php?msg_id=29898591
>
> and was proposed as
>From dd0900a74f5aa6d1c9ec0b7b556cf2f882928229 Mon Sep 17 00:00:00 2001
From: Olivier Fourdan
Date: Tue, 2 Oct 2012 16:48:48 +0200
Subject: [PATCH 2/2] data: update the database entry with status LED
Adds the newly supported field "ModeswitchLED" to the
relevant data files.
Signed-off-by: Oliv
>From 24cb3733ebc40c96a8bad7384797c50f64f49be6 Mon Sep 17 00:00:00 2001
From: Olivier Fourdan
Date: Tue, 2 Oct 2012 16:39:11 +0200
Subject: [PATCH 1/2] lib: add helper functions to get LED modeswitch group
Adds a new field "ModeswitchLED" to the libwacom
database definition file to specify whic
The following two patches is an attempt to implement the status LED logic
into libwacom.
The logic was discussed very recently in this thread:
http://sourceforge.net/mailarchive/message.php?msg_id=29898591
and was proposed as an inclusion in GNOME settings-daemon in bug 676558:
https://bugz
On Tue, 2012-10-02 at 15:20 +0200, Olivier Fourdan wrote:
> Hi all,
>
> While reviewing the libwacom API, I realized that
> libwacom_is_builtin() could be misleading:
>
>/**
> * @param device The tablet to query
> * @return non-zero if the device is built-in or zero if the device
>
Hi all,
While reviewing the libwacom API, I realized that
libwacom_is_builtin() could be misleading:
/**
* @param device The tablet to query
* @return non-zero if the device is built-in or zero if the device
is an
* external tablet
*/
int libwacom_is_builtin(WacomDevice *d
12 matches
Mail list logo
