Age | Commit message (Collapse) | Author | Files | Lines |
|
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
CC wcmXCommand.lo
../../src/wcmXCommand.c: In function 'wcmSetActionProperty':
../../src/wcmXCommand.c:460:23: warning: assignment discards 'const' qualifier from pointer target type [enabled by default]
case BadMatch: msg = "BadMatch"; break;
^
../../src/wcmXCommand.c:461:23: warning: assignment discards 'const' qualifier from pointer target type [enabled by default]
case BadValue: msg = "BadValue"; break;
^
../../src/wcmXCommand.c:462:17: warning: assignment discards 'const' qualifier from pointer target type [enabled by default]
default: msg = "UNKNOWN"; break;
^
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
src/wcmUSB.c:451:14: warning: unused variable 'private' [-Wunused-variable]
wcmUSBData* private = common->private;
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
The data in the property is actually the other way round. Oops.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
It is a Wacom device found in Fujitsu Lifebook T902.
Signed-off-by: Stephan Frank <sfrank@cs.tu-berlin.de>
Acked-by: Ping Cheng <pingc@wacom.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
|
|
wcmBTNChannel was statically assigned to PAD_CHANNEL by commit 1f9bf45b, which
excluded button events for CURSOR tools. This patch allows usbParseBTNEvent
to process button events for both CURSOR and PAD tools.
wcmBTNChannel is removed from wcmUSBData since we do not need it anymore.
Signed-off-by: Ping Cheng <pingc@wacom.com>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
|
|
Tested with a tablet pc, allowing finger scrolling in GTK3.
Signed-off-by: Jan Alexander Steffens (heftig) <jan.steffens@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
Tested-by: Jason Gerecke <killertofu@gmail.com>
|
|
The extra wcmEvent call was to deal with generic PAD events received
without motion events in the same packet. Those PAD events would be
filtered out by the device type retrieving code later.
Signed-off-by: Ping Cheng <pingc@wacom.com>
Acked-by: Chris Bagwell <chris@cnpbagwell.com>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
|
|
usbInitToolType retrieves device type from the kernel when tool
is on the tablet at X server startup. No need to do it again later.
Since kernel does not have a specific device type for PAD, we have
to check the actual events to set its type.
Signed-off-by: Ping Cheng <pingc@wacom.com>
Acked-by: Chris Bagwell <chris@cnpbagwell.com>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
|
|
Make room to report pen and touch events simultaneously
Signed-off-by: Ping Cheng <pingc@wacom.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
|
|
And do nothing.
USB devices are handled by the kernel, so we don't need to reset the HW.
ISDV4 devices don't get reset on normal shutdown anyway, so we don't need to
do anything here either.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
../src/wcmXCommand.c: In function 'wcmCheckActionProperty':
../src/wcmXCommand.c:387:3: warning: format '%d' expects argument of type 'int', but argument 4 has type 'long int' [-Wformat]
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
Devices with different product ids for pen and touch, such as
Cintiq 24HD and DTH 2242, were added recently. Applying arbitration
only for tools with same product id is not enough.
However, we want to make sure tools with same product id are lined
properly first. That's why the same routine is repeated instead of
combined.
Signed-off-by: Ping Cheng <pingc@wacom.com>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
|
|
We do not allow finger competes with CURSOR.
Signed-off-by: Ping Cheng <pingc@wacom.com>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
|
|
Arbitration did not work as expected since common is meant for tools
on the same logical port, not for tools of the same physical device
or of the same product id. Plus, not all devices support touch.
Signed-off-by: Ping Cheng <pingc@wacom.com>
Acked-by: Jason Gerecke <killertofu@gmail.com>
|
|
We shouldn't make *any* change to the state if checkonly==true, but
we've been resetting properties anyway. This blocks off the calls
to the reset functions to prevent them from being called if it's
just a drill.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
We did not explicitly add this option when worked on the manpage
since we thought Gnome control center (g-c-c) or something else
in userland would take care of touch (as well as its gestures).
However, I see no sign of getting touch in g-c-c soon. Let's take
care of touch uers here for now.
Wacom manpage is also updated accordingly.
Reported-by: Nikolai Neff <gefrierbrand@users.sf.net>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Ping Cheng <pinglinux@gmail.com>
|
|
Combined with the "#ifndef" in commit c95c1f2c, this fixes the compiler
warnings generated about ARRAY_SIZE being redefined.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
We can guarantee that the out arguments are non-NULL if the property
was found, so return a boolean instead of relying on the caller to
check for non-NULL results.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
While the NONE Atom indicates that the driver should reset the
action at the index it resides it, it is not *itself* a valid
action. This patch prevents us from attempting to set NONE as
an action.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Instead of checking only the 'actions' property, also check the
individual 'action' properties as well. We obviously won't be able
to correctly apply the former if the latter fails midway through.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Errors when setting an action property should not be swallowed. Note
that because the containing function does not bother to call this
function 'checkonly', clients still can't find out about errors
until its too late. We'll fix this in the next commit.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Ping Cheng <pinglinux@gmail.com>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
|
|
If wcmFindProp cannot find the given property, it will return a
negative error code. At the moment, this is taken as the success
condition(!?) for the strip_actions case... Aside from being
wrong, this has the potential to cause some nasty memory corruption.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
The existing code is needlessly hard to follow. It should return
immediately upon success, and unconditionally bail if it never
succeeded.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Actions specify X11 button numbers that should be generated when
performed. The maximum button number that could be used in an event
has been raised from the driver-imposed limit (WCM_MAX_BUTTON) to
the server-imposed limit (WCM_MAX_X11BUTTON).
This feature is necessary for gnome-settings-daemon to work properly.
To reliably identify each touch strip and ring, g-s-d assigns each
a high button numbers to send for each direction. Without this
patch, the driver ignores the actions set by g-s-d and continues
to send whatever the default action is instead.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Sprinkles a few extra DBG() calls into the code to make it a little
easier to track down issues with property-setting code.
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
see https://lists.gnu.org/archive/html/automake/2012-12/msg00038.html
- Support for the long-deprecated INCLUDES variable will be
removed altogether in Automake 1.14. The AM_CPPFLAGS variable should be
used instead.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Acked-by: Ping Cheng <pinglinux@gmail.com>
|
|
The server doesn't interpret %g, use %f instead. tbh, right now it doesn't
interpret %f either, but there's patches on the way for that.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Acked-by: Ping Cheng <pinglinux@gmail.com>
|
|
These two are never set to anything but 0 since
xf86-input-wacom-0.10.10-19-g6f5f29b
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Ping Cheng <pinglinux@gmail.com>
|
|
No functional changes.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
The server provides this macro in its headers, so only redefine it where
needed (for the tools)
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
Signed-off-by: Jason Gerecke <killertofu@gmail.com>
|
|
priv->wcmDeviceType contains the guessed device type, after querying the key
state from the kernel. If that found our device type, use it.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Tested-by: Jason Gerecke <killertofu@gmail.com>
|
|
Causing this function to always return 0
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Ping Cheng <pinglinux@gmail.com>
Tested-by: Jason Gerecke <killertofu@gmail.com>
|
|
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Signed-off-by: Ping Cheng <pinglinux@gmail.com>
Tested-by: Jason Gerecke <killertofu@gmail.com>
|
|
DOUBLETAP and TRIPLETAP are duplicated events in type-B MT format.
We do not use them in this driver. Plus, they could be confused
by fake MT events on older kernels.
Signed-off-by: Ping Cheng <pinglinux@gmail.com>
|
|
BTNChannel is static for all devices, not just geneic devices.
Signed-off-by: Ping Cheng <pinglinux@gmail.com>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
|
|
BTN_TOOL_FINGER indicates single touch/first finger if MT is enabled
Signed-off-by: Ping Cheng <pingc@wacom.com>
Reviewed-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Chris Bagwell <chris@cnpbagwell.com>
|
|
If we wait until we finish other verifications, we could miss
PAD events since they will be filtered out when there are no
motion events sent simultaneously.
Signed-off-by: Ping Cheng <pinglinux@gmail.com>
Acked-by: Jason Gerecke <killertofu@gmail.com>
|
|
wcmBTNChannel is only used by generic PAD device.
And it is statically assigned to PAD_CHANNEL. No
need to reassign it for every packet.
Signed-off-by: Ping Cheng <pinglinux@gmail.com>
Acked-by: Jason Gerecke <killertofu@gmail.com>
Reviewed-by: Chris Bagwell <chris@cnpbagwell.com>
|
|
We use true MT protocol for MT devices in kernel now. This code
was introduced to deal with ABS_TOOL_*TAP events loss issue. It
is uncessary any more. And its existence makes it hard to support
generic PAD cleanly.
Signed-off-by: Ping Cheng <pingc@wacom.com>
Acked-by: Jason Gerecke <killertofu@gmail.com>
|
|
Update man-page for driver behavior.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Ping Cheng <pinglinux@gmail.com>
|
|
Somehow we forgot Lenovo W700 last round.
Signed-off-by: Ping Cheng <pingc@wacom.com>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|
|
We upscaled resolutions in WacomModelDesc and reported from
absinfos. But we forgot to update them for older kernels
that do not support resolution in absinfo.
Resolution received from kernel is in hundredths of a mm.
The scale we use here is in meter.
Signed-off-by: Ping Cheng <pingc@wacom.com>
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
|