[Linuxwacom-devel] libwacom: [PATCH 1/3] lib: use kernel flags if available
From 11d5e6d38e8237d131153aa5a963393e295208b8 Mon Sep 17 00:00:00 2001
From: Olivier Fourdan ofour...@redhat.com
Date: Thu, 11 Oct 2012 10:32:10 +0200
Subject: [PATCH 1/3] lib: use kernel flags if available
to identify screen tablets if not set in the database.
To properly ensure the device is a screen tablet
check DIRECT flag is set but not POINTER.
Signed-off-by: Olivier Fourdan ofour...@redhat.com
---
configure.ac|1 +
libwacom/libwacom.c | 28 +---
2 files changed, 26 insertions(+), 3 deletions(-)
diff --git a/configure.ac b/configure.ac
index 64f4890..3079c5e 100644
--- a/configure.ac
+++ b/configure.ac
@@ -31,6 +31,7 @@ AC_CHECK_PROG(HAVE_DOXYGEN, [doxygen], [yes], [no])
AM_CONDITIONAL(HAVE_DOXYGEN, test x$HAVE_DOXYGEN = xyes)
PKG_CHECK_MODULES(GLIB, glib-2.0 gudev-1.0)
+AC_CHECK_HEADERS(linux/input.h)
PKG_CHECK_MODULES(LIBXML, libxml-2.0 glib-2.0, HAVE_LIBXML=yes, HAVE_LIBXML=no)
AM_CONDITIONAL(HAVE_LIBXML, test x$HAVE_LIBXML = xyes)
diff --git a/libwacom/libwacom.c b/libwacom/libwacom.c
index 25efa1b..d1a 100644
--- a/libwacom/libwacom.c
+++ b/libwacom/libwacom.c
@@ -34,6 +34,19 @@
#include string.h
#include gudev/gudev.h
+#ifdef HAVE_LINUX_INPUT_H
+#include linux/input.h
+#endif
+
+/* Defined in linux/input.h but older versions may be missing these definitions */
+#ifndef INPUT_PROP_POINTER
+#define INPUT_PROP_POINTER 0x00 /* needs a pointer */
+#endif
+
+#ifndef INPUT_PROP_DIRECT
+#define INPUT_PROP_DIRECT 0x01 /* direct input devices */
+#endif
+
static const WacomDevice *
libwacom_get_device(WacomDeviceDatabase *db, const char *match)
{
@@ -163,10 +176,19 @@ get_device_info (const char *path,
if (g_file_get_contents (sysfs_path, contents, NULL, NULL)) {
int flag;
- /* 0x01: POINTER flag
- * 0x02: DIRECT flag */
flag = atoi(contents);
- *builtin = (flag 0x02) == 0x02 ? IS_BUILTIN_TRUE : IS_BUILTIN_FALSE;
+ flag = (1 INPUT_PROP_DIRECT) | (1 INPUT_PROP_POINTER);
+ /*
+ * To ensure we are dealing with a screen tablet, need
+ * to check that it has DIRECT and non-POINTER (DIRECT
+ * alone is not sufficient since it's set for drawing
+ * tablets as well)
+ */
+ if (flag == (1 INPUT_PROP_DIRECT))
+*builtin = IS_BUILTIN_TRUE;
+ else
+*builtin = IS_BUILTIN_FALSE;
+
g_free (contents);
}
g_free (sysfs_path);
--
1.7.1
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] libwacom: [PATCH 2/3] data: add the IntegratedIn field to the tablet definitions
From 2b5b09ec4691e1fa239bee43fcf038c679b3eeeb Mon Sep 17 00:00:00 2001 From: Olivier Fourdan ofour...@redhat.com Date: Mon, 8 Oct 2012 16:02:39 +0200 Subject: [PATCH 2/3] data: add the IntegratedIn field to the tablet definitions If set, IntegratedIn specifies if the device is integrated in the Display (screen tablet) and/or System (ISD, TabletPC). This field supersedes the BuiltIn value. Signed-off-by: Olivier Fourdan ofour...@redhat.com --- data/bamboo-2fg-4x5.tablet|1 - data/bamboo-2fg-6x8.tablet|1 - data/bamboo-2fg.tablet|1 - data/bamboo-craft.tablet |1 - data/bamboo-one.tablet|1 - data/bamboo-pen.tablet|1 - data/cintiq-12wx.tablet |2 +- data/cintiq-20wsx.tablet |2 +- data/cintiq-21ux.tablet |2 +- data/cintiq-21ux2.tablet |2 +- data/cintiq-22hd.tablet |2 +- data/cintiq-24hd.tablet |2 +- data/dtf-720.tablet |2 +- data/dti-520.tablet |2 +- data/dtu-1631.tablet |2 +- data/dtu-2231.tablet |2 +- data/generic.tablet |1 - data/graphire-wireless-8x6.tablet |1 - data/intuos4-12x19.tablet |1 - data/intuos4-4x6.tablet |1 - data/intuos4-6x9-wl.tablet|1 - data/intuos4-6x9.tablet |1 - data/intuos4-8x13.tablet |1 - data/intuos5-m.tablet |1 - data/intuos5-s.tablet |1 - data/intuos5-touch-l.tablet |1 - data/intuos5-touch-m.tablet |1 - data/intuos5-touch-s.tablet |1 - data/isdv4-90.tablet |2 +- data/isdv4-93.tablet |2 +- data/isdv4-e3.tablet |2 +- data/isdv4-e6.tablet |2 +- data/isdv4-ed.tablet |2 +- data/isdv4-ef.tablet |2 +- data/n-trig-pen.tablet|2 +- data/serial-wacf004.tablet|2 +- data/wacom.example| 12 +--- 37 files changed, 23 insertions(+), 43 deletions(-) diff --git a/data/bamboo-2fg-4x5.tablet b/data/bamboo-2fg-4x5.tablet index fb0cb90..812638f 100644 --- a/data/bamboo-2fg-4x5.tablet +++ b/data/bamboo-2fg-4x5.tablet @@ -20,7 +20,6 @@ Stylus=true Reversible=true Touch=true Buttons=4 -BuiltIn=false [Buttons] Left=A;B;C;D diff --git a/data/bamboo-2fg-6x8.tablet b/data/bamboo-2fg-6x8.tablet index d7bf97c..c9288d8 100644 --- a/data/bamboo-2fg-6x8.tablet +++ b/data/bamboo-2fg-6x8.tablet @@ -20,7 +20,6 @@ Stylus=true Reversible=true Touch=true Buttons=4 -BuiltIn=false [Buttons] Left=A;B;C;D diff --git a/data/bamboo-2fg.tablet b/data/bamboo-2fg.tablet index 4e74ccd..ffea220 100644 --- a/data/bamboo-2fg.tablet +++ b/data/bamboo-2fg.tablet @@ -19,7 +19,6 @@ Stylus=false Reversible=true Touch=true Buttons=4 -BuiltIn=false [Buttons] Left=A;B;C;D diff --git a/data/bamboo-craft.tablet b/data/bamboo-craft.tablet index e68ca5d..dc1bfce 100644 --- a/data/bamboo-craft.tablet +++ b/data/bamboo-craft.tablet @@ -20,7 +20,6 @@ Stylus=true Reversible=true Touch=true Buttons=4 -BuiltIn=false [Buttons] Left=A;B;C;D diff --git a/data/bamboo-one.tablet b/data/bamboo-one.tablet index feacf54..1d553a8 100644 --- a/data/bamboo-one.tablet +++ b/data/bamboo-one.tablet @@ -13,4 +13,3 @@ Touch=false Ring=false NumStrips=0 Buttons=0 -BuiltIn=false diff --git a/data/bamboo-pen.tablet b/data/bamboo-pen.tablet index a5b5aea..a897b71 100644 --- a/data/bamboo-pen.tablet +++ b/data/bamboo-pen.tablet @@ -19,4 +19,3 @@ Stylus=true Reversible=true Touch=false Buttons=0 -BuiltIn=false diff --git a/data/cintiq-12wx.tablet b/data/cintiq-12wx.tablet index 006500d..75b2457 100644 --- a/data/cintiq-12wx.tablet +++ b/data/cintiq-12wx.tablet @@ -38,12 +38,12 @@ Width=10 Height=7 Layout=cintiq-12wx.svg Styli=0x913;0x91b;0x813;0x81b;0x823;0x82b;0x801;0x885; +IntegratedIn=Display [Features] Stylus=true NumStrips=2 Buttons=10 -BuiltIn=true [Buttons] Left=A;B;C;D;I diff --git a/data/cintiq-20wsx.tablet b/data/cintiq-20wsx.tablet index 3cc6c23..4bc91d0 100644 --- a/data/cintiq-20wsx.tablet +++ b/data/cintiq-20wsx.tablet @@ -40,13 +40,13 @@ Class=Cintiq Width=17 Height=11 Styli=0x913;0x91b;0x813;0x81b;0x823;0x82b;0x801;0x885; +IntegratedIn=Display [Features] Reversible=false Stylus=true NumStrips=2 Buttons=14 -BuiltIn=true [Buttons] Left=A;B;C;D;I;K;L diff --git a/data/cintiq-21ux.tablet b/data/cintiq-21ux.tablet index 30d3922..1c353a4 100644 --- a/data/cintiq-21ux.tablet +++ b/data/cintiq-21ux.tablet @@ -33,13 +33,13 @@ Class=Cintiq Width=17 Height=13 Styli=0x913;0x91b;0x813;0x81b;0x823;0x82b;0x801;0x885; +IntegratedIn=Display [Features] Reversible=false Stylus=true NumStrips=2 Buttons=8 -BuiltIn=true [Buttons] Left=A;B;C;D diff --git a/data/cintiq-21ux2.tablet b/data/cintiq-21ux2.tablet index 85f2686..734f9f3 100644
[Linuxwacom-devel] libwacom: [PATCH 3/3] lib: add IntegratedIn to device group
From 15f93f5d3bd9f2aefd59a5087b2ce44a3c53403c Mon Sep 17 00:00:00 2001
From: Olivier Fourdan ofour...@redhat.com
Date: Thu, 11 Oct 2012 12:04:45 +0200
Subject: [PATCH 3/3] lib: add IntegratedIn to device group
to describe integrated system devices and screen tablets.
A bit field allows to identify the level of integration of
a device:
WACOM_DEVICE_INTEGRATED_NONEdevice is a standalone tablet
WACOM_DEVICE_INTEGRATED_DISPLAY device is a screen tablet
WACOM_DEVICE_INTEGRATED_SYSTEM device is an ISD such as
a tablet PC.
Or -1 (WACOM_DEVICE_INTEGRATED_UNSET) if the information is not
available
These definitions supersede the previous libwacom_is_builtin()
API which is now deprecated.
Signed-off-by: Olivier Fourdan ofour...@redhat.com
---
libwacom/libwacom-database.c | 59 ++--
libwacom/libwacom.c | 67 +
libwacom/libwacom.h | 24 ++-
libwacom/libwacomint.h | 10 +-
4 files changed, 113 insertions(+), 47 deletions(-)
diff --git a/libwacom/libwacom-database.c b/libwacom/libwacom-database.c
index bbea114..ae73239 100644
--- a/libwacom/libwacom-database.c
+++ b/libwacom/libwacom-database.c
@@ -256,6 +256,14 @@ struct {
{ Touchstrip2, WACOM_STATUS_LED_TOUCHSTRIP2 }
};
+struct {
+ const char *key;
+ WacomIntegrationFlags value;
+} integration_flags[] = {
+ { Display, WACOM_DEVICE_INTEGRATED_DISPLAY },
+ { System, WACOM_DEVICE_INTEGRATED_SYSTEM }
+};
+
static void
libwacom_parse_buttons_key(WacomDevice *device,
GKeyFile *keyfile,
@@ -329,8 +337,7 @@ libwacom_parse_tablet_keyfile(const char *datadir, const char *filename)
char *layout;
char *class;
char *match;
- char **styli_list;
- char **leds_list;
+ char **string_list;
keyfile = g_key_file_new();
@@ -361,31 +368,50 @@ libwacom_parse_tablet_keyfile(const char *datadir, const char *filename)
device-name = g_key_file_get_string(keyfile, DEVICE_GROUP, Name, NULL);
device-width = g_key_file_get_integer(keyfile, DEVICE_GROUP, Width, NULL);
device-height = g_key_file_get_integer(keyfile, DEVICE_GROUP, Height, NULL);
+
+ device-integration_flags = WACOM_DEVICE_INTEGRATED_UNSET;
+ string_list = g_key_file_get_string_list(keyfile, DEVICE_GROUP, IntegratedIn, NULL, NULL);
+ if (string_list) {
+ guint i, n;
+
+ device-integration_flags = WACOM_DEVICE_INTEGRATED_NONE;
+ for (i = 0; string_list[i]; i++) {
+ for (n = 0; n G_N_ELEMENTS (integration_flags); n++) {
+if (!strcmp(string_list[i], integration_flags[n].key)) {
+ device-integration_flags |= integration_flags[n].value;
+ break;
+}
+ }
+ }
+ g_strfreev (string_list);
+ }
+
layout = g_key_file_get_string(keyfile, DEVICE_GROUP, Layout, NULL);
if (layout) {
/* For the layout, we store the full path to the SVG layout */
device-layout = g_build_filename (datadir, layouts, layout, NULL);
g_free (layout);
}
+
class = g_key_file_get_string(keyfile, DEVICE_GROUP, Class, NULL);
device-cls = libwacom_class_string_to_enum(class);
g_free(class);
- styli_list = g_key_file_get_string_list(keyfile, DEVICE_GROUP, Styli, NULL, NULL);
- if (styli_list) {
+ string_list = g_key_file_get_string_list(keyfile, DEVICE_GROUP, Styli, NULL, NULL);
+ if (string_list) {
GArray *array;
guint i;
array = g_array_new (FALSE, FALSE, sizeof(int));
device-num_styli = 0;
- for (i = 0; styli_list[i]; i++) {
- glong long_value = strtol (styli_list[i], NULL, 0);
+ for (i = 0; string_list[i]; i++) {
+ glong long_value = strtol (string_list[i], NULL, 0);
int int_value = long_value;
g_array_append_val (array, int_value);
device-num_styli++;
}
- g_strfreev (styli_list);
+ g_strfreev (string_list);
device-supported_styli = (int *) g_array_free (array, FALSE);
} else {
device-supported_styli = g_new (int, 2);
@@ -407,15 +433,13 @@ libwacom_parse_tablet_keyfile(const char *datadir, const char *filename)
if (g_key_file_get_boolean(keyfile, FEATURES_GROUP, Ring2, NULL))
device-features |= FEATURE_RING2;
- if (g_key_file_get_boolean(keyfile, FEATURES_GROUP, BuiltIn, NULL))
- device-features |= FEATURE_BUILTIN;
-
if (g_key_file_get_boolean(keyfile, FEATURES_GROUP, Reversible, NULL))
device-features |= FEATURE_REVERSIBLE;
- if (device-features FEATURE_BUILTIN
+ if (device-integration_flags != WACOM_DEVICE_INTEGRATED_UNSET
+ device-integration_flags WACOM_DEVICE_INTEGRATED_DISPLAY
device-features FEATURE_REVERSIBLE)
- g_warning (Tablet '%s' is both reversible and builtin. This is impossible, libwacom_get_match(device));
+ g_warning (Tablet '%s' is both reversible and integrated in screen. This is impossible, libwacom_get_match(device));
if (!(device-features FEATURE_RING)
(device-features FEATURE_RING2))
@@ -433,22 +457,23 @@ libwacom_parse_tablet_keyfile(const char *datadir, const char *filename)
[Linuxwacom-devel] libwacom: buttons location missing?
Hi, Working on the layout definitions here, on the default layout to be precise, ie the layout that would be returned if no SVG layout is provided. I found some tablet definitions such as the graphire-wireless-8x6.tablet which have 2 buttons but no indication of the actual button location, ie: Buttons=2 but no # Location of the buttons Left= Right= Top= Bottom= Is that a valid data file? Without the actual buttons' location, the info is fairly useless to guess the layout... Cheers, Olivier -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom: libwacom_is_builtin() misleading?
On Tue, Oct 2, 2012 at 6:20 AM, Olivier Fourdan ofour...@redhat.com 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 is an * external tablet */ int libwacom_is_builtin(WacomDevice *device); From the description, I would expect built-in tablets (such as the one used for Tablet PC) to have that set to true, and all other external tablet to have that property set to false. Actually, what libwacom_is_builtin() means is that the tablet is a screen tablet, so all Cintiq have that property set to true, even though these are actually external tablets. Problem is in some cases it would interesting to tell if a tablet is actually built-in or external (for example to set the TabletPC mode automatically) and using libwacom_is_builtin() is not appropriate for that. While I understand all built-in tablets are screen tablets, not all screen tablets are built-in IMHO. Is that my own interpration of the above which is wrong or is it the function name/description which is misleading? And if it's the function name, any idea on how we could fix this nicely? GNOME setttings daemon does use libwacom_is_builtin() to determine if a tablet is a screen tablet (e.g. Cintiq). How about introducing a new keyword and function for Tablet PCs? We can use libwacom_is_tabletpc() or libwacom_is_isd(), where isd stands for Integrated System Device. Then updating the description for libwacom_is_builtin() to clarify the difference. Are you going to update libwacom? Ping -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom: libwacom_is_builtin() misleading?
Hi Ping, Ping Cheng said the following on 10/05/2012 06:14 PM: On Tue, Oct 2, 2012 at 6:20 AM, Olivier Fourdanofour...@redhat.com wrote: [...] And if it's the function name, any idea on how we could fix this nicely? GNOME setttings daemon does use libwacom_is_builtin() to determine if a tablet is a screen tablet (e.g. Cintiq). How about introducing a new keyword and function for Tablet PCs? We can use libwacom_is_tabletpc() or libwacom_is_isd(), where isd stands for Integrated System Device. Then updating the description for libwacom_is_builtin() to clarify the difference. Are you going to update libwacom? If we reach a general consensus that this is useful, needed and welcome in libwacom, I shall happily submit patches to add that this API :-) Cheers, Olivier. -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom: libwacom_is_builtin() misleading?
On Fri, Oct 5, 2012 at 9:20 AM, Olivier Fourdan ofour...@redhat.com wrote: Hi Ping, Ping Cheng said the following on 10/05/2012 06:14 PM: On Tue, Oct 2, 2012 at 6:20 AM, Olivier Fourdanofour...@redhat.com wrote: [...] And if it's the function name, any idea on how we could fix this nicely? GNOME setttings daemon does use libwacom_is_builtin() to determine if a tablet is a screen tablet (e.g. Cintiq). How about introducing a new keyword and function for Tablet PCs? We can use libwacom_is_tabletpc() or libwacom_is_isd(), where isd stands for Integrated System Device. Then updating the description for libwacom_is_builtin() to clarify the difference. Are you going to update libwacom? If we reach a general consensus that this is useful, needed and welcome in libwacom, I shall happily submit patches to add that this API :-) Both Jason and I think it is the way to go. Thank you for asking. Ping -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] libwacom: libwacom_is_builtin() misleading?
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 *device); From the description, I would expect built-in tablets (such as the one used for Tablet PC) to have that set to true, and all other external tablet to have that property set to false. Actually, what libwacom_is_builtin() means is that the tablet is a screen tablet, so all Cintiq have that property set to true, even though these are actually external tablets. Problem is in some cases it would interesting to tell if a tablet is actually built-in or external (for example to set the TabletPC mode automatically) and using libwacom_is_builtin() is not appropriate for that. While I understand all built-in tablets are screen tablets, not all screen tablets are built-in IMHO. Is that my own interpration of the above which is wrong or is it the function name/description which is misleading? And if it's the function name, any idea on how we could fix this nicely? GNOME setttings daemon does use libwacom_is_builtin() to determine if a tablet is a screen tablet (e.g. Cintiq). Cheers Olivier. -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom: libwacom_is_builtin() misleading?
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 is an * external tablet */ int libwacom_is_builtin(WacomDevice *device); From the description, I would expect built-in tablets (such as the one used for Tablet PC) to have that set to true, and all other external tablet to have that property set to false. Actually, what libwacom_is_builtin() means is that the tablet is a screen tablet, so all Cintiq have that property set to true, even though these are actually external tablets. Built-in means that the tablet is built into the screen. Feel free to change the documentation if it's not clear. Cheers -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] libwacom release coming up
we've had a few additions to libwacom, so it's time for another release (0.6). If there are any patches or bugs I've missed please let me know. small ticket items only (e.g. data definition files). This release will also bump the soname from 2:0:0 to 3:0:1. this version didn't actually change the library much, but 0.5 did and we didn't bump the soname then. Cheers, Peter -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom new data file 'make check' error
On Mon, 2012-05-21 at 22:28 -0500, Favux ... wrote:
I'd appreciate some help on this one. I do not know why I am seeing
on 'make check':
lt-tablet-validity: tablet-validity.c:94: verify_tablet: Assertion
`nstyli == 1' failed.
/bin/bash: line 5: 8362 Aborted (core dumped) ${dir}$tst
FAIL: tablet-validity
===
1 of 3 tests failed
===
From this .tablet file. It's the first of the 3 and they all seem OK
to me. Don't understand why the stylus is flagged.
Can't find this assertion in git master.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom new data file 'make check' error
On Tue, May 22, 2012 at 8:33 AM, Bastien Nocera had...@hadess.net wrote:
On Mon, 2012-05-21 at 22:28 -0500, Favux ... wrote:
I'd appreciate some help on this one. I do not know why I am seeing
on 'make check':
lt-tablet-validity: tablet-validity.c:94: verify_tablet: Assertion
`nstyli == 1' failed.
/bin/bash: line 5: 8362 Aborted (core dumped) ${dir}$tst
FAIL: tablet-validity
===
1 of 3 tests failed
===
From this .tablet file. It's the first of the 3 and they all seem OK
to me. Don't understand why the stylus is flagged.
Can't find this assertion in git master.
Strange. I have a vanilla clone:
libwacom$ git branch -r
origin/HEAD - origin/master
origin/master
Alright then. I'll submit the set to be looked at.
Dave
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom new data file 'make check' error
On Tue, 2012-05-22 at 09:11 -0500, Favux ... wrote:
On Tue, May 22, 2012 at 8:33 AM, Bastien Nocera had...@hadess.net wrote:
On Mon, 2012-05-21 at 22:28 -0500, Favux ... wrote:
I'd appreciate some help on this one. I do not know why I am seeing
on 'make check':
lt-tablet-validity: tablet-validity.c:94: verify_tablet: Assertion
`nstyli == 1' failed.
/bin/bash: line 5: 8362 Aborted (core dumped) ${dir}$tst
FAIL: tablet-validity
===
1 of 3 tests failed
===
From this .tablet file. It's the first of the 3 and they all seem OK
to me. Don't understand why the stylus is flagged.
Can't find this assertion in git master.
Strange. I have a vanilla clone:
libwacom$ git branch -r
origin/HEAD - origin/master
origin/master
$ git grep assert | grep nstyli
test/tablet-validity.c: assert(nstyli = 1);
test/tablet-validity.c: assert(eraser_is_present (db, styli,
nstyli, type));
Alright then. I'll submit the set to be looked at.
Dave
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom new data file 'make check' error
So commit 4a7a7f16564869b3af6701aa943e5c88927f451b ? test: Test each stylus with an eraser -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom new data file 'make check' error
On Tue, 2012-05-22 at 10:01 -0500, Favux ... wrote: So commit 4a7a7f16564869b3af6701aa943e5c88927f451b ? test: Test each stylus with an eraser The message you posted said it crashed on line 94. This is line 94: 94 ↦ ↦ ↦ break;• -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom new data file 'make check' error
On Tue, May 22, 2012 at 10:04 AM, Bastien Nocera had...@hadess.net wrote: On Tue, 2012-05-22 at 10:01 -0500, Favux ... wrote: So commit 4a7a7f16564869b3af6701aa943e5c88927f451b ? test: Test each stylus with an eraser The message you posted said it crashed on line 94. This is line 94: 94 ↦ ↦ ↦ break;• The clone has an up to date 'git pull'. For me line #94 is: assert(nstyli == 1); And: break; is 95. Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom new data file 'make check' error
Oh shoot. I'm wrong. I missed the last commit daac0e51d32eb2000e1a7bf48a0ffb018e7c6c7c test: remove special-case for DTI-520 Have to test with that. Sorry for the noise. Dave -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom new data file 'make check' error
On Tue, May 22, 2012 at 11:24:49AM -0500, Favux ... wrote: I must be doing something silly. I checked with a new clone and the HEAD doesn't point to the last commit daac0e5, it points to the one before f195cf3. So to get a tablet-validity.c without the DTI520 special case in it I have to do a 'git checkout daac0e5'. Because it is the same on both I doubt I've messed up the history. I just tested with a new clone and everything appears to be in order. are you rebasing? what's your master branch at? (I recommend installing tig or gitk, they show the branch names and tags on the commits, so it's a lot easier to find out what's going on) Cheers, Peter -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] libwacom new data file 'make check' error
I'd appreciate some help on this one. I do not know why I am seeing
on 'make check':
lt-tablet-validity: tablet-validity.c:94: verify_tablet: Assertion
`nstyli == 1' failed.
/bin/bash: line 5: 8362 Aborted (core dumped) ${dir}$tst
FAIL: tablet-validity
===
1 of 3 tests failed
===
From this .tablet file. It's the first of the 3 and they all seem OK
to me. Don't understand why the stylus is flagged.
Dave
0001-data-add-ISDV4-90-tablet.patch
Description: Binary data
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom
On Sun, 2012-02-05 at 10:49 -0600, Favux ... wrote: I've long suspected that if the stylus will work with the digitizer on a consumer tablet then all the stylus hardware will work too. So if your BambooPT was a Pen model without an eraser a Bamboo Pen Touch model stylus with an eraser would have a working eraser even on the Pen. And the same with the tablet PCs. However I can recall only a few folks reporting this; apparently getting a new stylus isn't very common. So it is good you confirm it Jason. Given that is true then we don't want to restrict stylus or other capabilities for consumer tablets in libwacom. So the upshot is whether the different capabilities of the stylus need to be take into account in the applet. For example something that has been constantly seen since the xorg.conf days is folks having a section for the cursor even though their tablet doesn't come with a mouse/puck. However just like the stylus I suspect if the base model supports a puck then their tablet would even though it was packaged without one. Apparently a lot think the cursor refers to the pointer arrow rather than another input tool. If the applet is presenting them with options to configure a non-existent cursor, stylus side switch or eraser people will be trying to configure them. And then asking why that doesn't work. A lot of people with their first Wacom tablet don't realize what a Wacom eraser looks like and don't know if they have one or not or that it only works in eraser enabled programs. We don't apply any configuration to the Wacom tablet mice in GNOME. We consider them to be a way to save some desk space. We also don't support the Lens cursor (which I gather is just a mouse with a crosshair attached). It would be a good thing if the Wacom tablet applet's interface somehow helped clear up confusion over the input tools. Through tool tips? May be asking too much, but at least something to keep in the back of the mind. What do you want the UI to do? The name will already be generic stylus. I don't think we can go much further than that. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom
On Mon, Feb 06, 2012 at 02:08:49PM +, Bastien Nocera wrote: We also don't support the Lens cursor (which I gather is just a mouse with a crosshair attached). I don't know how many of those wacom actually sell (but I do know professional mapping people who use such devices) - for anyone who does have one though, being able to calibrate it accurately does seem like a rather essential step to making it useful. I can understand if they aren't a high priority at this stage, but designing something which would rule them out (or consider them to be 'just another mouse') would seem like a mistake ... Cheers, Ron -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom
I've long suspected that if the stylus will work with the digitizer on a consumer tablet then all the stylus hardware will work too. So if your BambooPT was a Pen model without an eraser a Bamboo Pen Touch model stylus with an eraser would have a working eraser even on the Pen. And the same with the tablet PCs. However I can recall only a few folks reporting this; apparently getting a new stylus isn't very common. So it is good you confirm it Jason. Given that is true then we don't want to restrict stylus or other capabilities for consumer tablets in libwacom. So the upshot is whether the different capabilities of the stylus need to be take into account in the applet. For example something that has been constantly seen since the xorg.conf days is folks having a section for the cursor even though their tablet doesn't come with a mouse/puck. However just like the stylus I suspect if the base model supports a puck then their tablet would even though it was packaged without one. Apparently a lot think the cursor refers to the pointer arrow rather than another input tool. If the applet is presenting them with options to configure a non-existent cursor, stylus side switch or eraser people will be trying to configure them. And then asking why that doesn't work. A lot of people with their first Wacom tablet don't realize what a Wacom eraser looks like and don't know if they have one or not or that it only works in eraser enabled programs. It would be a good thing if the Wacom tablet applet's interface somehow helped clear up confusion over the input tools. Through tool tips? May be asking too much, but at least something to keep in the back of the mind. Favux -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom
Favux ... favux.is@... writes: An initial libwacom page: https://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Libwacom I think the information about filling in the definition files should be in wacom.example directly, and nothing (that would most likely end up being outdated) in the Wiki. The contributors list, which you seem to have snarfed from my blog entry, are the contributors to the GNOME wacom support, not to libwacom. For example, Jason didn't contribute until I committed his extensive definition files. Other than that, the content is interesting, thanks. is now posted on the Developer Pages: https://sourceforge.net/apps/mediawiki/linuxwacom/index.php? title=Category:DeveloperPages I do have another question. When I look at the GNOME 3.4 Control Panel Wacom tablet applet rotation seems to apply the stylus parent device. I can't tell if touch is also rotated for USB tablet PCs and BambooPTs with their separate parent device for touch. Is it? Does it show up as a separate tool? If so, we don't support it yet in GsdWacomDevice, but adding it should be enough to get all the tools rotated at once. Can you file a bug against gnome-settings-daemon in the GNOME Bugzilla for that? Cheers -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom
Hi Bastien, Thanks for reviewing the wiki page. On Thu, Feb 2, 2012 at 10:31 AM, Bastien Nocera had...@hadess.net wrote: I think the information about filling in the definition files should be in wacom.example directly, and nothing (that would most likely end up being outdated) in the Wiki. So loose the intuos4-wl definition file? The contributors list, which you seem to have snarfed from my blog entry, are the contributors to the GNOME wacom support, not to libwacom. For example, Jason didn't contribute until I committed his extensive definition files. Will correct that then. Yes everything is cribbed off your blog and other posts and interviews. And some of Peter's stuff. If there is any original content it is probably accidental. :) Other than that, the content is interesting, thanks. I don't know if you are interested but if you want to have at it and edit it Peter can add you to the wiki editor list. I do have another question. When I look at the GNOME 3.4 Control Panel Wacom tablet applet rotation seems to apply the stylus parent device. I can't tell if touch is also rotated for USB tablet PCs and BambooPTs with their separate parent device for touch. Is it? Does it show up as a separate tool? If so, we don't support it yet in GsdWacomDevice, but adding it should be enough to get all the tools rotated at once. Can you file a bug against gnome-settings-daemon in the GNOME Bugzilla for that? When tested touch rotates fine for my BambooPT but not for my usb tablet PC. That's with GNOME 3.2 as I haven't tested it yet with the GNOME 3.4 Control Panel. The BambooPT's pad buttons don't rotate of course, but you haven't started working on those. A further issue concerns the generic styli. The LLC (low low cost) consumer tablets like the Bamboo Pen and the Bamboo Ones have a stylus + 2 buttons but no eraser. That's true of some of the tablet PCs also. Additionally if I recall correctly some tablet PCs have a stylus + 1 button. Not sure if those styli have erasers or not. On those models the driver tends to report a spurious eraser and pad (with the tablets) in say 'xinput list'. Since libwacom removes the reporting of a spurious pad (Buttons=0) doing the same for the eraser or spurious side button would be nice. Maybe Peter can tell us which styli those are? Favux -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom
I meant Jason not Peter re the styli. -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom
On Thu, 2012-02-02 at 11:55 -0600, Favux ... wrote: Hi Bastien, Thanks for reviewing the wiki page. On Thu, Feb 2, 2012 at 10:31 AM, Bastien Nocera had...@hadess.net wrote: I think the information about filling in the definition files should be in wacom.example directly, and nothing (that would most likely end up being outdated) in the Wiki. I rather meant the advices about the naming of the device for example. You also probably want to use a definition that doesn't have FIXME in it as the example ;) The contributors list, which you seem to have snarfed from my blog entry, are the contributors to the GNOME wacom support, not to libwacom. For example, Jason didn't contribute until I committed his extensive definition files. Will correct that then. Yes everything is cribbed off your blog and other posts and interviews. And some of Peter's stuff. If there is any original content it is probably accidental. :) Haha. Other than that, the content is interesting, thanks. I don't know if you are interested but if you want to have at it and edit it Peter can add you to the wiki editor list. I do have another question. When I look at the GNOME 3.4 Control Panel Wacom tablet applet rotation seems to apply the stylus parent device. I can't tell if touch is also rotated for USB tablet PCs and BambooPTs with their separate parent device for touch. Is it? Does it show up as a separate tool? If so, we don't support it yet in GsdWacomDevice, but adding it should be enough to get all the tools rotated at once. Can you file a bug against gnome-settings-daemon in the GNOME Bugzilla for that? When tested touch rotates fine for my BambooPT but not for my usb tablet PC. That's with GNOME 3.2 as I haven't tested it yet with the GNOME 3.4 Control Panel. The BambooPT's pad buttons don't rotate of course, but you haven't started working on those. A further issue concerns the generic styli. The LLC (low low cost) consumer tablets like the Bamboo Pen and the Bamboo Ones have a stylus + 2 buttons but no eraser. Ha, I didn't know that. We need to create some new styli for those devices then. Peter, Jason, any advice on what tool IDs we could use for those? That's true of some of the tablet PCs also. Additionally if I recall correctly some tablet PCs have a stylus + 1 button. It's really the same problem. My Bluetooth graphire-based tablet has 2 buttons, and an eraser. We need separate styli definition for them. Not sure if those styli have erasers or not. On those models the driver tends to report a spurious eraser and pad (with the tablets) in say 'xinput list'. Since libwacom removes the reporting of a spurious pad (Buttons=0) doing the same for the eraser or spurious side button would be nice. Maybe Peter can tell us which styli those are? We don't count the tips. So a stylus always has one button, and an eraser always has one button. We would use HasEraser=false for the stylus though. Cheers -- Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom
On Thu, Feb 2, 2012 at 12:31 PM, Bastien Nocera had...@hadess.net wrote: On Thu, 2012-02-02 at 11:55 -0600, Favux ... wrote: Hi Bastien, Thanks for reviewing the wiki page. On Thu, Feb 2, 2012 at 10:31 AM, Bastien Nocera had...@hadess.net wrote: I think the information about filling in the definition files should be in wacom.example directly, and nothing (that would most likely end up being outdated) in the Wiki. I rather meant the advices about the naming of the device for example. You also probably want to use a definition that doesn't have FIXME in it as the example ;) The contributors list, which you seem to have snarfed from my blog entry, are the contributors to the GNOME wacom support, not to libwacom. For example, Jason didn't contribute until I committed his extensive definition files. Will correct that then. Yes everything is cribbed off your blog and other posts and interviews. And some of Peter's stuff. If there is any original content it is probably accidental. :) Haha. Other than that, the content is interesting, thanks. I don't know if you are interested but if you want to have at it and edit it Peter can add you to the wiki editor list. I do have another question. When I look at the GNOME 3.4 Control Panel Wacom tablet applet rotation seems to apply the stylus parent device. I can't tell if touch is also rotated for USB tablet PCs and BambooPTs with their separate parent device for touch. Is it? Does it show up as a separate tool? If so, we don't support it yet in GsdWacomDevice, but adding it should be enough to get all the tools rotated at once. Can you file a bug against gnome-settings-daemon in the GNOME Bugzilla for that? When tested touch rotates fine for my BambooPT but not for my usb tablet PC. That's with GNOME 3.2 as I haven't tested it yet with the GNOME 3.4 Control Panel. The BambooPT's pad buttons don't rotate of course, but you haven't started working on those. A further issue concerns the generic styli. The LLC (low low cost) consumer tablets like the Bamboo Pen and the Bamboo Ones have a stylus + 2 buttons but no eraser. Ha, I didn't know that. We need to create some new styli for those devices then. Peter, Jason, any advice on what tool IDs we could use for those? I've not yet played with libwacom or new Gnome wacom work (trying to wait until 2/7 when Fedora is supposed to branch from rawhide before I upgrade a VM+software but its getting harder to wait.). So I don't know some of these terms but here is some extra info that may be important. Some models of Bamboo in same family+generation are sold with stylus that have erasers. I think, but I'm not sure, that its only a packaging issue to save a few bucks and if you buy a replacement stylus from same family+generation with an eraser that it would work. Unfortunately, all my styli have erasers so I can not test this theory. That is only reason I've not pursued hiding the BTN_TOOL_ERASER on these Bamboo devices in kernel driver. I'd hate to take away a feature from users. I'm not sure how this would translate into libwacom or Gnome support but the concept of Delayed Hotplugging that's been discussed in the past may be useful here. That's true of some of the tablet PCs also. Additionally if I recall correctly some tablet PCs have a stylus + 1 button. It's really the same problem. My Bluetooth graphire-based tablet has 2 buttons, and an eraser. We need separate styli definition for them. Not sure if those styli have erasers or not. On those models the driver tends to report a spurious eraser and pad (with the tablets) in say 'xinput list'. Since libwacom removes the reporting of a spurious pad (Buttons=0) doing the same for the eraser or spurious side button would be nice. Maybe Peter can tell us which styli those are? We don't count the tips. So a stylus always has one button, and an eraser always has one button. We would use HasEraser=false for the stylus though. Here is some more info related to my Bamboo comment. For Tablet PC's (the ones that usually say something about ISDv4 in dmesg), I don't have any personal experience but from reports I see it seems like for a given generation there is only 1 type of stylus (maybe it has 0, 1, or 2 buttons beyond the tip button and maybe it has an eraser or not). If you share a stylus between Tablet PC families+generations with different buttons/eraser config there is a good change it will work for stylus+tip but everything else is iffy. For this cases, I think its probably best to take effort to hide erasers and unsupported buttons per USB PID inside the kernel driver. Its minor driver changes if my assumption could be proven 100% accurate (which I can't do since I've never touch a Wacom Tablet PC). But it also sounds like we are going to be able to hide it with configuration file as well; which is great. Chris
Re: [Linuxwacom-devel] libwacom
On Thu, Feb 2, 2012 at 12:09 PM, Chris Bagwell ch...@cnpbagwell.com wrote: On Thu, Feb 2, 2012 at 12:31 PM, Bastien Nocera had...@hadess.net wrote: On Thu, 2012-02-02 at 11:55 -0600, Favux ... wrote: Hi Bastien, Thanks for reviewing the wiki page. On Thu, Feb 2, 2012 at 10:31 AM, Bastien Nocera had...@hadess.net wrote: I think the information about filling in the definition files should be in wacom.example directly, and nothing (that would most likely end up being outdated) in the Wiki. I rather meant the advices about the naming of the device for example. You also probably want to use a definition that doesn't have FIXME in it as the example ;) The contributors list, which you seem to have snarfed from my blog entry, are the contributors to the GNOME wacom support, not to libwacom. For example, Jason didn't contribute until I committed his extensive definition files. Will correct that then. Yes everything is cribbed off your blog and other posts and interviews. And some of Peter's stuff. If there is any original content it is probably accidental. :) Haha. Other than that, the content is interesting, thanks. I don't know if you are interested but if you want to have at it and edit it Peter can add you to the wiki editor list. I do have another question. When I look at the GNOME 3.4 Control Panel Wacom tablet applet rotation seems to apply the stylus parent device. I can't tell if touch is also rotated for USB tablet PCs and BambooPTs with their separate parent device for touch. Is it? Does it show up as a separate tool? If so, we don't support it yet in GsdWacomDevice, but adding it should be enough to get all the tools rotated at once. Can you file a bug against gnome-settings-daemon in the GNOME Bugzilla for that? When tested touch rotates fine for my BambooPT but not for my usb tablet PC. That's with GNOME 3.2 as I haven't tested it yet with the GNOME 3.4 Control Panel. The BambooPT's pad buttons don't rotate of course, but you haven't started working on those. A further issue concerns the generic styli. The LLC (low low cost) consumer tablets like the Bamboo Pen and the Bamboo Ones have a stylus + 2 buttons but no eraser. Ha, I didn't know that. We need to create some new styli for those devices then. Peter, Jason, any advice on what tool IDs we could use for those? As I mentioned in another thread, consumer devices don't report stylus information. If we're getting pen data, all we know is that the tablet and pen's technologies are compatible... We can't tell how many side switches it has, whether there's an eraser, etc. I've not yet played with libwacom or new Gnome wacom work (trying to wait until 2/7 when Fedora is supposed to branch from rawhide before I upgrade a VM+software but its getting harder to wait.). So I don't know some of these terms but here is some extra info that may be important. Some models of Bamboo in same family+generation are sold with stylus that have erasers. I think, but I'm not sure, that its only a packaging issue to save a few bucks and if you buy a replacement stylus from same family+generation with an eraser that it would work. Unfortunately, all my styli have erasers so I can not test this theory. That is only reason I've not pursued hiding the BTN_TOOL_ERASER on these Bamboo devices in kernel driver. I'd hate to take away a feature from users. I'm not sure how this would translate into libwacom or Gnome support but the concept of Delayed Hotplugging that's been discussed in the past may be useful here. That's true of some of the tablet PCs also. Additionally if I recall correctly some tablet PCs have a stylus + 1 button. It's really the same problem. My Bluetooth graphire-based tablet has 2 buttons, and an eraser. We need separate styli definition for them. Not sure if those styli have erasers or not. On those models the driver tends to report a spurious eraser and pad (with the tablets) in say 'xinput list'. Since libwacom removes the reporting of a spurious pad (Buttons=0) doing the same for the eraser or spurious side button would be nice. Maybe Peter can tell us which styli those are? We don't count the tips. So a stylus always has one button, and an eraser always has one button. We would use HasEraser=false for the stylus though. Here is some more info related to my Bamboo comment. For Tablet PC's (the ones that usually say something about ISDv4 in dmesg), I don't have any personal experience but from reports I see it seems like for a given generation there is only 1 type of stylus (maybe it has 0, 1, or 2 buttons beyond the tip button and maybe it has an eraser or not). If you share a stylus between Tablet PC families+generations with different buttons/eraser config there is a good change it will work for stylus+tip but everything else is iffy. I don't have much practical experience with the ISDv4
Re: [Linuxwacom-devel] libwacom
On Sat, Jan 28, 2012 at 01:04:40PM -0600, Favux ... wrote: Is linuxwacom-devel the correct mailing list to submit patches for libwacom? Or is there another mailing list that should be used? Yeah, that was the plan, especially since I hope that eventually the driver will make use of libwacom as well. Cheers, Peter -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] libwacom
Thank you. An initial libwacom page: https://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Libwacom is now posted on the Developer Pages: https://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Category:DeveloperPages I do have another question. When I look at the GNOME 3.4 Control Panel Wacom tablet applet rotation seems to apply the stylus parent device. I can't tell if touch is also rotated for USB tablet PCs and BambooPTs with their separate parent device for touch. Is it? Favux -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
