Nabble - linuxwacom-devel

How to properly unload wacom module (using xf86DeleteInputDriver)?

2009-11-28T09:47:12Z

Hi,
According to this:

http://www.x.org/wiki/XOrgInputDriverSpec#head-b9066edbe89a1d9f2ecf0398e7ec94c4dd65e8a8

xf86DeleteInputDriver should be called in ModuleTearDownProc to remove
the module from the list of available modules. DeleteInputDriver
requires index number as an argument and I cannot see a way to get this
number.
I want to properly unload module to be able to load it again without
xserver restart. I checked synaptics, evdev, intel video and ati drivers
and I couldn't find one module that uses xf86DeleteInputDriver (or
xf86DeleteDriver for video drivers)...
Am I missing something?

Now the same problem just in a different way:
what you're doing after modifying the module to test the changes? Are
you restarting xserver every time to reload the module?

--
Kind regards,
Przemo

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[RFC] xf86-input-wacom guidelines

2009-11-27T09:49:09Z

Dnia 2009-11-22, nie o godzinie 14:05 -0800, Ping pisze:

> However, this is an open source project. You can provide a guideline
> for us or share your suggestions with us. We are more than happy to
> accept any contributions to the project, especially for
> xf86-input-wacom, which bears our future. We want, by all means, to
> make it easier for others to contribue to linuxwacom project.

OK, here is first sketch of proposed changes in the structure of the
driver:

wcmCommon.c - contains all funcions required for handling a tablet
(receiving, handling, sending events), but not for
initializing/opening/closing/configuring tablet or manipulating data).
xf86WcmOpen should be in xf86Wacom.c

wcmCompat.c - DELETE. xf86WcmWait to be moved to wcmISDV4.c (it's used
only there) xf86WcmReady be moved to wcmWacom.c (it's used only there)

wcmConfig.c - allocating device, initialising, plugging, unplugging,
uninitialising. xf86WcmPointInArea, xf86WcmAreasOverlap,
xf86WcmAreaListOverlap should be moved to wcmCommon

wcmFilter.c - data filtering (like pressure curve functions or jitter
correction, tilt2rotation)

wcmFilter.h - header file for wcmFilter.c

wcmISDV4.c - Wacom IV protocol specific functions

wcmTilt2Rotation.c - DELETE. Function xf86WcmTilt2R to be moved to
wcmFilter, tiltTable to go to wcmFilter.h

wcmUSB.c - USB specific functions. WacomModel definitions to be moved to
a new wcmUSB.h header file. Another option is to create wcmConfig.h and
drop all USB and ISDV4 definitions there.

wcmValidateDevice.c - probing, parsing, checking for duplicate device

wcmXCommand.c - Mode switching and screen changing functions,
xf86WcmSetProperty and InitWcmDeviceProperties to be moved to
xf86Config.c

xf86Wacom.c - opening, closing device, change control. Option 2: merge
xf86Wacom with wcmConfig. xf86WcmRegisterX11Devices to be moved to
wcmConfig.c and xf86WcmIsWacomDevice to wcmValidateDevice.c

My goal is to create a logical structure, easy to understand by a
newcomer. A next thing is that if you, lets say, want to check some USB
functions you don't need to see all the properties of all USB tablets
(even nicely folded by vim), that's why I added a separate header file
with the definitions. I'm sure it can be done better, so I'm open to all
suggestions.

--
regards,
Przemo

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [PATCH] - very minor fixes

2009-11-25T13:09:35Z

On Tue, Nov 24, 2009 at 08:56:51PM -0800, Ping wrote:

> > In addition, the comment style changes between the files.
> > I'm not adverse to having proper doxygen comments instead, but I'm also not
> > adverse to simply remove comments like (fake example):
> > /* xf86WcmAddTwoNumbers - adds two numbers */
> >
>
> xf86-input-wacom is in your $HOME. Feel free to change it to whatever
> format/style you like. I don't have an attachment to the existing style.
> If you have a preferred style for xf86-input-wacom, please share with us. I
> am willing to go with any style as long as we get the job done. As for the
> "good habit" part, it takes time to adapt, especially for the "old dogs"
> like me.
>
> Fair?

sure, but please consider (and I want this publicly stated here :) that it's
in my $HOME because that was easily available when we forked it. once the
big cleanup is done, it'll likely move to a more permanent place.

in terms of style: I try to use whatever style is used in the surrounding
code or the same file. I'm not a big fan of /*********/ comments, especially
if they don't convey information (writing good comments is hard,
surprisingly so). removing those won't affect the code, so I might just do
that in a spare and bored minute.

in terms of style, that's the only thing I'd drop though, the rest doesn't
really matter enough to really worry about it.

in terms of changing contributions: sometimes I change them in minor matters
(e.g. indentation or commit messages), but not the code itself. I have found
though that asking a developer to resubmit a patch with minor changes is
better than fixing it up myself - simply because it scales better. I think
it's a fair assumption that someone who's willing to write a patch is also
ok with fixing up a few tabs and spaces.

Cheers,
Peter

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [PATCH] - very minor fixes

2009-11-25T12:50:06Z

On Wed, Nov 25, 2009 at 08:34:41PM +0000, Przemysław Firszt wrote:

> Dnia 2009-11-25, śro o godzinie 10:39 +1000, Peter Hutterer pisze:
> > Przemo - please use the git commit messages as a tool to convey the reason
> > behind the patch (not necessarily the method, it's often obvious).
> > git commits are cheap, git log is cheap and I find myself reading log files
> > more often than the actual code they change. With hundreds of commits and
> > several repositories to keep track of, it becomes quite important to be able
> > to find commits and _understand_ commits quickly. as a general rule, if you
> > were to just send the patch, the commit message should convey enough
> > information why one should review and apply the patch - without even looking
> > at the source.
> >
> > commit messages like "comment fixed" have little meaning in that regard. In
> > this case something more explanatory is
> > "Fix comment - xf86WcmInitalprivSize is actually xf86WcmInitialToolSize"
> > or, for the other patch
> > "Remove duplicate comment for xf86WcmRegisterX11Devices.
> >
> > This function still exists, a duplicate comment got accidentally added in
> > 425351f22821ade814f7f6412d18c1eb25904661."
> >
> Peter,
> I really appreciate your comments and I'll stick to those rules next
> time. Do you really want me to add hash No. to commit messages? ;-) (I
> just learnt how to use "git blame")

if it makes sense for a particular message - yes please. it's not needed
that often though so just use common sense.

fwiw, I recommend checking out 'tig' as well, it's great for navigating git
logs and has a vastly superior git blame interface.

Cheers,
Peter

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [PATCH] - very minor fixes

2009-11-25T12:34:41Z

Dnia 2009-11-25, śro o godzinie 10:39 +1000, Peter Hutterer pisze:

> Przemo - please use the git commit messages as a tool to convey the reason
> behind the patch (not necessarily the method, it's often obvious).
> git commits are cheap, git log is cheap and I find myself reading log files
> more often than the actual code they change. With hundreds of commits and
> several repositories to keep track of, it becomes quite important to be able
> to find commits and _understand_ commits quickly. as a general rule, if you
> were to just send the patch, the commit message should convey enough
> information why one should review and apply the patch - without even looking
> at the source.
>
> commit messages like "comment fixed" have little meaning in that regard. In
> this case something more explanatory is
> "Fix comment - xf86WcmInitalprivSize is actually xf86WcmInitialToolSize"
> or, for the other patch
> "Remove duplicate comment for xf86WcmRegisterX11Devices.
>
> This function still exists, a duplicate comment got accidentally added in
> 425351f22821ade814f7f6412d18c1eb25904661."
>

Peter,
I really appreciate your comments and I'll stick to those rules next
time. Do you really want me to add hash No. to commit messages? ;-) (I
just learnt how to use "git blame")

--
Przemo

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [PATCH] - very minor fixes

2009-11-24T20:56:51Z

2009/11/24 Peter Hutterer <peter.hutterer@...>

Ping - this is personal preference but I notice that most of these comments
serve little purpose, either they're not enough to actually explain what the
function does or they're quite obvious by the function name.

To be honest, there is nothing personal about this project, except it is my job instead of my hobby :). That is, I am responsible to maintain a working driver all the time.

I kinda followed the format/convention that was introduced by previous developers, especially by Fred and John. Furthermore, when I get a patch from someone, I usually don't change their code if the code passes testing. I don't feel it is necessary to turn a contribution off by its style, considering all contributions are so important to the success of this project :).

I follow the kernel patch format when submitting kernel patches and I used to follow XFree86 format to submit patches to them.

In an ideal world, this project serves as a "middleware" which processes user feedbacks, develops unstable driver for broader testing, attracts volunteers to make contributions, and eventually provides kernel and X server stable drivers that can be included into open source systems. However, we are not living in an ideal world. So, this project is not just a middleware, at least not yet.

In addition, the comment style changes between the files.
I'm not adverse to having proper doxygen comments instead, but I'm also not
adverse to simply remove comments like (fake example):
/* xf86WcmAddTwoNumbers - adds two numbers */

xf86-input-wacom is in your $HOME. Feel free to change it to whatever format/style you like. I don't have an attachment to the existing style. If you have a preferred style for xf86-input-wacom, please share with us. I am willing to go with any style as long as we get the job done. As for the "good habit" part, it takes time to adapt, especially for the "old dogs" like me.

Fair?

Ping

Any comments?

> From acf166c340333efc3303ce836501c2bb5af3fa06 Mon Sep 17 00:00:00 2001
> From: Przemo Firszt <przemo@...>
> Date: Tue, 24 Nov 2009 20:57:31 +0000
> Subject: [PATCH 2/2] Comment fixed
>
> ---
> src/xf86Wacom.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c
> index 5b8778d..160fd60 100644
> --- a/src/xf86Wacom.c
> +++ b/src/xf86Wacom.c
> @@ -581,7 +581,7 @@ static struct { KeySym keysym; CARD8 mask; } keymod[] = {
> #endif
>
> /*****************************************************************************
> - * xf86WcmInitialprivSize --
> + * xf86WcmInitialToolSize --
> * Initialize logical size and resolution for individual tool.
> ****************************************************************************/
>
> --
> 1.6.5.2

Przemo - please use the git commit messages as a tool to convey the reason
behind the patch (not necessarily the method, it's often obvious).
git commits are cheap, git log is cheap and I find myself reading log files
more often than the actual code they change. With hundreds of commits and
several repositories to keep track of, it becomes quite important to be able
to find commits and _understand_ commits quickly. as a general rule, if you
were to just send the patch, the commit message should convey enough
information why one should review and apply the patch - without even looking
at the source.

commit messages like "comment fixed" have little meaning in that regard. In
this case something more explanatory is
"Fix comment - xf86WcmInitalprivSize is actually xf86WcmInitialToolSize"
or, for the other patch
"Remove duplicate comment for xf86WcmRegisterX11Devices.

This function still exists, a duplicate comment got accidentally added in
425351f22821ade814f7f6412d18c1eb25904661."

Of course, I am being extra-picky here. In these cases it is obvious and the
only change comments, but it's a good habit to get into. think of those poor
developers who have too little time ;)

That aside, thanks for the patches, I've merged them both (with extended
modified commit messages) and will push them in a tick.

Cheers,
Peter

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [PATCH] - very minor fixes

2009-11-24T16:39:55Z

On Tue, Nov 24, 2009 at 09:20:38PM +0000, Przemysław Firszt wrote:

> From 4cf5a249e2abc489ce671a277d72ec14af202392 Mon Sep 17 00:00:00 2001
> From: Przemo Firszt <przemo@...>
> Date: Tue, 24 Nov 2009 20:50:39 +0000
> Subject: [PATCH 1/2] Duplicate comment removed
>
> ---
> src/xf86Wacom.c | 6 ------
> 1 files changed, 0 insertions(+), 6 deletions(-)
>
> diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c
> index 6b76039..5b8778d 100644
> --- a/src/xf86Wacom.c
> +++ b/src/xf86Wacom.c
> @@ -435,12 +435,6 @@ void xf86WcmInitialCoordinates(LocalDevicePtr local, int axes)
> return;
> }
>
> -/*****************************************************************************
> - * xf86WcmRegisterX11Devices --
> - * Register the X11 input devices with X11 core.
> - ****************************************************************************/
> -
> -
> #if GET_ABI_MAJOR(ABI_XINPUT_VERSION) < 5
> /* Define our own keymap so we can send key-events with our own device and not
> * rely on inputInfo.keyboard */
> --
> 1.6.5.2

Merged, thanks.

Ping - this is personal preference but I notice that most of these comments
serve little purpose, either they're not enough to actually explain what the
function does or they're quite obvious by the function name.
In addition, the comment style changes between the files.
I'm not adverse to having proper doxygen comments instead, but I'm also not
adverse to simply remove comments like (fake example):
/* xf86WcmAddTwoNumbers - adds two numbers */

Any comments?

> From acf166c340333efc3303ce836501c2bb5af3fa06 Mon Sep 17 00:00:00 2001
> From: Przemo Firszt <przemo@...>
> Date: Tue, 24 Nov 2009 20:57:31 +0000
> Subject: [PATCH 2/2] Comment fixed
>
> ---
> src/xf86Wacom.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c
> index 5b8778d..160fd60 100644
> --- a/src/xf86Wacom.c
> +++ b/src/xf86Wacom.c
> @@ -581,7 +581,7 @@ static struct { KeySym keysym; CARD8 mask; } keymod[] = {
> #endif
>
> /*****************************************************************************
> - * xf86WcmInitialprivSize --
> + * xf86WcmInitialToolSize --
> * Initialize logical size and resolution for individual tool.
> ****************************************************************************/
>
> --
> 1.6.5.2

Przemo - please use the git commit messages as a tool to convey the reason
behind the patch (not necessarily the method, it's often obvious).
git commits are cheap, git log is cheap and I find myself reading log files
more often than the actual code they change. With hundreds of commits and
several repositories to keep track of, it becomes quite important to be able
to find commits and _understand_ commits quickly. as a general rule, if you
were to just send the patch, the commit message should convey enough
information why one should review and apply the patch - without even looking
at the source.

commit messages like "comment fixed" have little meaning in that regard. In
this case something more explanatory is
"Fix comment - xf86WcmInitalprivSize is actually xf86WcmInitialToolSize"
or, for the other patch
"Remove duplicate comment for xf86WcmRegisterX11Devices.

This function still exists, a duplicate comment got accidentally added in
425351f22821ade814f7f6412d18c1eb25904661."

Of course, I am being extra-picky here. In these cases it is obvious and the
only change comments, but it's a good habit to get into. think of those poor
developers who have too little time ;)

That aside, thanks for the patches, I've merged them both (with extended
modified commit messages) and will push them in a tick.

Cheers,
Peter

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[PATCH] - very minor fixes

2009-11-24T13:20:38Z

Fixed typos/duplications in comments - see attachment for details.

--
Przemo

[0001-Duplicate-comment-removed.patch]

>From 4cf5a249e2abc489ce671a277d72ec14af202392 Mon Sep 17 00:00:00 2001 From: Przemo Firszt <przemo@...> Date: Tue, 24 Nov 2009 20:50:39 +0000 Subject: [PATCH 1/2] Duplicate comment removed --- src/xf86Wacom.c | 6 ------ 1 files changed, 0 insertions(+), 6 deletions(-) diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c index 6b76039..5b8778d 100644 --- a/src/xf86Wacom.c +++ b/src/xf86Wacom.c @@ -435,12 +435,6 @@ void xf86WcmInitialCoordinates(LocalDevicePtr local, int axes) return; } -/***************************************************************************** - * xf86WcmRegisterX11Devices -- - * Register the X11 input devices with X11 core. - ****************************************************************************/ - - #if GET_ABI_MAJOR(ABI_XINPUT_VERSION) < 5 /* Define our own keymap so we can send key-events with our own device and not * rely on inputInfo.keyboard */ -- 1.6.5.2

[0002-Comment-fixed.patch]

>From acf166c340333efc3303ce836501c2bb5af3fa06 Mon Sep 17 00:00:00 2001 From: Przemo Firszt <przemo@...> Date: Tue, 24 Nov 2009 20:57:31 +0000 Subject: [PATCH 2/2] Comment fixed --- src/xf86Wacom.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c index 5b8778d..160fd60 100644 --- a/src/xf86Wacom.c +++ b/src/xf86Wacom.c @@ -581,7 +581,7 @@ static struct { KeySym keysym; CARD8 mask; } keymod[] = { #endif /***************************************************************************** - * xf86WcmInitialprivSize -- + * xf86WcmInitialToolSize -- * Initialize logical size and resolution for individual tool. ****************************************************************************/ -- 1.6.5.2

Re: FW: [PATCH] xf86-input-wacom

2009-11-24T12:35:57Z

Re: FW: [PATCH] xf86-input-wacom

2009-11-22T14:05:15Z

2009/11/22 Przemysław Firszt <przemo@...>

Dnia 2009-11-19, czw o godzinie 12:00 +1000, Peter Hutterer pisze:
> now, moving these structs and the associated bits over to xf86Wacom.c makes
> sense in principle, though right now the distinction between what goes into
> wcmConfig.c and xf86Wacom.c isn't quite clear to me. hence I don't really
> see the point of moving it around for now until we've sorted out why there's
> two different files for it :)
Ping, do we have a guideline what should be where?

That's a good question. The short answer would be no. But that answer doesn't even make myself feel comfortable. There is a history on what we have now. Initially, there was only one file which is xf86Wacom.c. When John Joganic created this project about 7 years ago, he refactored the code and made it easier for us to maintain. I guess, wcmConfig.c was intended only to deal with configuration related stuff. Those routines that have a closer tie to XFree86, such as xf86WcmDevConvert, xf86WcmDevReverseConvert, xf86WcmDevProc, etc., stayed. I have added a few new files while introducing new features. With so many features and new models to support, halting the development for a whole code refactoring was something I could not afford.

However, this is an open source project. You can provide a guideline for us or share your suggestions with us. We are more than happy to accept any contributions to the project, especially for xf86-input-wacom, which bears our future. We want, by all means, to make it easier for others to contribue to linuxwacom project.

Ping

Re: FW: [PATCH] xf86-input-wacom

2009-11-22T10:56:44Z

Dnia 2009-11-19, czw o godzinie 12:00 +1000, Peter Hutterer pisze:
[..]
> I'm not a big fan of changes like this in an otherwise unrelated patches.
> the wcmFilter removal seems to fit into the previous patch, doesn't it? i'll
> squash it in there.
You're right - I'll do it that way next time (same for the comment
below).
[..]
> now, moving these structs and the associated bits over to xf86Wacom.c makes
> sense in principle, though right now the distinction between what goes into
> wcmConfig.c and xf86Wacom.c isn't quite clear to me. hence I don't really
> see the point of moving it around for now until we've sorted out why there's
> two different files for it :)
Ping, do we have a guideline what should be where?

--
Regards,
Przemo

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[ANNOUNCE] xf86-input-wacom 0.10.1

2009-11-19T21:53:22Z

Release 0.10.1 of the xf86-input-wacom driver is now available.
Note that this driver currently resides in my $HOME on freedesktop.org.

http://cgit.freedesktop.org/~whot/xf86-input-wacom/

Loads of patches, mostly cleanup and aimed towards better hotplugging
support. Instead of relying on HAL directives, the driver now does its own
hotplugging based on the model found. To do so, the driver queries the
kernel for the tablet's capabilities and then sets up stylus, erasor, etc.
pending the matching keys set on the device.

Peter Hutterer (45):
Use the SYSCALL macro for opening the fd
Silence compiler warnings if DEBUG is off.
Abstract the vendor ID into a #define
Don't cast xalloc returns.
Streamline xf86WcmAllocate a bit
Localize lookup for other devices of the same device.
Unify log messages to a common format.
Move allocation of type out of xf86WcmInit
Fix a comment
Remove fakeLocal init device.
Don't overwrite the name with the XI type.
Remove needless NULL checks before xfree.
Use ARRAY_SIZE macro instead of manual sizeof().
Pass type into wcmIsAValidType.
Break out of the loop once we found a valid type.
Abstract product lookup into a static function.
On unplug, remove the device from the commonWcmDevices list.
Support auto-hotplugging in the driver.
Remove unecessary debug statements.
Don't accept invalid Rotate and ForceDevice options.
vim tags for the coding style.
BaudRate only needs checking for ISDV4 devices.
Remove Xfree86 4 serial wrapper defines
Remove some more useless defines.
Rip most option parsing out of xf86WcmInit.
Remove log spamming debug message.
Remove a needless call to xf86CheckStrOption
Move the uniq assignment into wcmNeedAutoHotplug.
Move auto-dev probing checks into small static function
Remove "grabbed event device" log message.
Export tool type as Wacom Tool Type property.
Don't fail just because it's not a wacom tablet.
Add 0xFF product as catchall for unknown devices.
Add wacom-properties header file.
Fix an error message to list the device name.
If a device is specified, don't check for a wacom vendor id.
Remove some if 0'd code.
Remove spurious executable bits from source files.
Add GPL document to dist tarball.
Fix long-standing typos in applying speed factors.
Remove REVISION HISTORY comments.
Remove defines from the ghost of christmas past.
Purge driver-specific speed/accel.
Fix comment in configure.
wacom 0.10.1

Ping Cheng (9):
Avoid adding duplicated devices/tools from hotplugging
Validate tool type before adding it
share device size and resolution between penabled and touch of the same product ID
process second finger touch data
report device id for protocol 5 devices
Spin-off validatation from configuration.
retrieve all tool types from the kernel
This patch allows multiple tools of the same type to be defined for one device.
Remove a duplicated #ifdef in wcmValidateDevice.c

Przemo Firszt (1):
Remove duplicate of #include "xf86Wacom.h" and #include "wcmFilter.h"

Thomas Jaeger (1):
Fix TPCButton option

git tag: xf86-input-wacom-0.10.1

http://people.freedesktop.org/~whot/xf86-input-wacom/xf86-input-wacom-0.10.1.tar.bz2
MD5: 544f40bb5bcdd8538c248c4067f3848f xf86-input-wacom-0.10.1.tar.bz2
SHA1: 106f7fcf9e4255b5b3efa29bccc8ed94d42cfb2d xf86-input-wacom-0.10.1.tar.bz2

http://people.freedesktop.org/~whot/xf86-input-wacom/xf86-input-wacom-0.10.1.tar.gz
MD5: aa7ab1aa876276ca2d8aac115671c841 xf86-input-wacom-0.10.1.tar.gz
SHA1: 0c3358ad37fb83024cdca2f2ed4ad219d74d1e97 xf86-input-wacom-0.10.1.tar.gz

Cheers,
Peter

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

attachment0 (205 bytes) Download Attachment

Re: FW: [PATCH] xf86-input-wacom

2009-11-18T18:00:46Z

sorry, I missed this one. my spamfilter got overly excited over the last
week. thanks Ping for forwarding it.

> >From f2ac561863aa95aad03a3975e8c1813391b306e9 Mon Sep 17 00:00:00 2001
> From: Przemo Firszt <przemo@...>
> Date: Fri, 13 Nov 2009 17:53:04 +0000
> Subject: [PATCH 1/3] Remove duplicate of #include "xf86Wacom.h" and #include "wcmFilter.h"
>
> ---
> src/xf86Wacom.c | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c
> index 58ecef0..029da44 100755
> --- a/src/xf86Wacom.c
> +++ b/src/xf86Wacom.c
> @@ -44,16 +44,13 @@
> */
>
> /****************************************************************************/
> -
> -#include "xf86Wacom.h"
> -#include "wcmFilter.h"
> -#include <sys/stat.h>
> -#include <fcntl.h>
> -
> #ifdef HAVE_CONFIG_H
> #include <config.h>
> #endif
>
> +#include <sys/stat.h>
> +#include <fcntl.h>
> +
> #include "xf86Wacom.h"
> #include "wcmFilter.h"
>
> @@ -61,6 +58,9 @@
> #include <xserver-properties.h>
> #endif
>
> +/*****************************************************************************
> + * Forward declaration
> + ****************************************************************************/
> void xf86WcmVirtaulTabletPadding(LocalDevicePtr local);
> void xf86WcmVirtaulTabletSize(LocalDevicePtr local);
> Bool xf86WcmIsWacomDevice (char* fname);
> --
> 1.6.5.2

applied, see next comment though.

> >From 3e6878ba7288ff71fc2d64d845fd71b91d1545f8 Mon Sep 17 00:00:00 2001
> From: Przemo Firszt <przemo@...>
> Date: Fri, 13 Nov 2009 18:24:42 +0000
> Subject: [PATCH 2/3] Add InputDriverRec
>
> ---
> src/xf86Wacom.c | 13 +++++++++++--
> 1 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c
> index 029da44..071b370 100755
> --- a/src/xf86Wacom.c
> +++ b/src/xf86Wacom.c
> @@ -52,8 +52,7 @@
> #include <fcntl.h>
>
> #include "xf86Wacom.h"
> -#include "wcmFilter.h"
> -
> +

I'm not a big fan of changes like this in an otherwise unrelated patches.
the wcmFilter removal seems to fit into the previous patch, doesn't it? i'll
squash it in there.

> #if GET_ABI_MAJOR(ABI_XINPUT_VERSION) >= 7
> #include <xserver-properties.h>
> #endif
> @@ -87,6 +86,16 @@ static Bool xf86WcmDevConvert(LocalDevicePtr local, int first, int num,
> static Bool xf86WcmDevReverseConvert(LocalDevicePtr local, int x, int y,
> int* valuators);
>
> +InputDriverRec WACOM = {
> + 1,
> + "wacom",
> + NULL,
> + NULL,
> + NULL,
> + NULL,
> + 0
> +};
> +
> WacomModule gWacomModule =
> {
> NULL, /* input driver pointer */
> --
> 1.6.5.2

we have this struct defined in wcmConfig.c, adding it here would duplicate
it.

> >From a99805846f3d5e41cda7834a925c9417dfa5c138 Mon Sep 17 00:00:00 2001
> From: Przemo Firszt <przemo@...>
> Date: Fri, 13 Nov 2009 18:25:37 +0000
> Subject: [PATCH 3/3] Add XF86ModuleVersionInfo
>
> ---
> src/xf86Wacom.c | 13 +++++++++++++
> 1 files changed, 13 insertions(+), 0 deletions(-)
>
> diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c
> index 071b370..0426f65 100755
> --- a/src/xf86Wacom.c
> +++ b/src/xf86Wacom.c
> @@ -96,6 +96,19 @@ InputDriverRec WACOM = {
> 0
> };
>
> +static XF86ModuleVersionInfo VersionRec = {
> + "wacom",
> + MODULEVENDORSTRING,
> + MODINFOSTRING1,
> + MODINFOSTRING2,
> + XORG_VERSION_CURRENT,
> + PACKAGE_VERSION_MAJOR, PACKAGE_VERSION_MINOR, PACKAGE_VERSION_PATCHLEVEL,
> + ABI_CLASS_XINPUT,
> + ABI_XINPUT_VERSION,
> + MOD_CLASS_XINPUT,
> + {0, 0, 0, 0}
> +};
> +
> WacomModule gWacomModule =
> {
> NULL, /* input driver pointer */
> --
> 1.6.5.2

same as with the above patch.

now, moving these structs and the associated bits over to xf86Wacom.c makes
sense in principle, though right now the distinction between what goes into
wcmConfig.c and xf86Wacom.c isn't quite clear to me. hence I don't really
see the point of moving it around for now until we've sorted out why there's
two different files for it :)

Cheers,
Peter

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

[PATCH] xf86-input-wacom

2009-11-17T11:57:15Z

Hi Ping, Peter,
Let me know if this is (see attached) what you're looking for when you
wrote that:
http://old.nabble.com/linuxwacom-and-xf86-input-wacom-plan-td25760339.html

--
Przemo

[0001-Remove-duplicate-of-include-xf86Wacom.h-and-include-.patch]

>From f2ac561863aa95aad03a3975e8c1813391b306e9 Mon Sep 17 00:00:00 2001 From: Przemo Firszt <przemo@...> Date: Fri, 13 Nov 2009 17:53:04 +0000 Subject: [PATCH 1/3] Remove duplicate of #include "xf86Wacom.h" and #include "wcmFilter.h" --- src/xf86Wacom.c | 12 ++++++------ 1 files changed, 6 insertions(+), 6 deletions(-) diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c index 58ecef0..029da44 100755 --- a/src/xf86Wacom.c +++ b/src/xf86Wacom.c @@ -44,16 +44,13 @@ */ /****************************************************************************/ - -#include "xf86Wacom.h" -#include "wcmFilter.h" -#include <sys/stat.h> -#include <fcntl.h> - #ifdef HAVE_CONFIG_H #include <config.h> #endif +#include <sys/stat.h> +#include <fcntl.h> + #include "xf86Wacom.h" #include "wcmFilter.h" @@ -61,6 +58,9 @@ #include <xserver-properties.h> #endif +/***************************************************************************** + * Forward declaration + ****************************************************************************/ void xf86WcmVirtaulTabletPadding(LocalDevicePtr local); void xf86WcmVirtaulTabletSize(LocalDevicePtr local); Bool xf86WcmIsWacomDevice (char* fname); -- 1.6.5.2

[0002-Add-InputDriverRec.patch]

>From 3e6878ba7288ff71fc2d64d845fd71b91d1545f8 Mon Sep 17 00:00:00 2001 From: Przemo Firszt <przemo@...> Date: Fri, 13 Nov 2009 18:24:42 +0000 Subject: [PATCH 2/3] Add InputDriverRec --- src/xf86Wacom.c | 13 +++++++++++-- 1 files changed, 11 insertions(+), 2 deletions(-) diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c index 029da44..071b370 100755 --- a/src/xf86Wacom.c +++ b/src/xf86Wacom.c @@ -52,8 +52,7 @@ #include <fcntl.h> #include "xf86Wacom.h" -#include "wcmFilter.h" - + #if GET_ABI_MAJOR(ABI_XINPUT_VERSION) >= 7 #include <xserver-properties.h> #endif @@ -87,6 +86,16 @@ static Bool xf86WcmDevConvert(LocalDevicePtr local, int first, int num, static Bool xf86WcmDevReverseConvert(LocalDevicePtr local, int x, int y, int* valuators); +InputDriverRec WACOM = { + 1, + "wacom", + NULL, + NULL, + NULL, + NULL, + 0 +}; + WacomModule gWacomModule = { NULL, /* input driver pointer */ -- 1.6.5.2

[0003-Add-XF86ModuleVersionInfo.patch]

>From a99805846f3d5e41cda7834a925c9417dfa5c138 Mon Sep 17 00:00:00 2001 From: Przemo Firszt <przemo@...> Date: Fri, 13 Nov 2009 18:25:37 +0000 Subject: [PATCH 3/3] Add XF86ModuleVersionInfo --- src/xf86Wacom.c | 13 +++++++++++++ 1 files changed, 13 insertions(+), 0 deletions(-) diff --git a/src/xf86Wacom.c b/src/xf86Wacom.c index 071b370..0426f65 100755 --- a/src/xf86Wacom.c +++ b/src/xf86Wacom.c @@ -96,6 +96,19 @@ InputDriverRec WACOM = { 0 }; +static XF86ModuleVersionInfo VersionRec = { + "wacom", + MODULEVENDORSTRING, + MODINFOSTRING1, + MODINFOSTRING2, + XORG_VERSION_CURRENT, + PACKAGE_VERSION_MAJOR, PACKAGE_VERSION_MINOR, PACKAGE_VERSION_PATCHLEVEL, + ABI_CLASS_XINPUT, + ABI_XINPUT_VERSION, + MOD_CLASS_XINPUT, + {0, 0, 0, 0} +}; + WacomModule gWacomModule = { NULL, /* input driver pointer */ -- 1.6.5.2

Re: serial wacom tablet and HAL/PolicyKit

2009-11-14T15:15:47Z

After more investigation, the problem is more on the udev process, wacom
related udev rules file, seem to only manage usb wacom, not device one.
/dev/ttyUSB0 is well created, but, in /dev/input, no eventX, wacom or
other device file is created.

Popolon a écrit :

> Has anyone managed a serial wacom (pluged via an USB-serial adapter) to
> autodetect HAL or Policykit ?
> If anyone managed to have an autodetection by HAL or PolicyKit on a
> direct USB plug, this could be helpfull too.
>
> My USB WACOM is autodetected by hal (hotplug), but not my serial (on usb
> adapter) one.
>
> the adapter is well detected by the kernel, that's :
> Prolific PL2303 USB to serial adaptor driver
>
> a /dev/ttyUSB0 is created.
>
> wacdump /dev/ttyUSB0 works well (on some retry, it doesn't work, I have
> to deplug/replug the usb adapter from the pc).
>
> It gives me on the model part :
>
> MODEL=Wacom Intuos 9x12 ROM=1.1-7
> CLS=Serial VNDR=Wacom DEV=Intuos SUB=GD-0912-R
>
>
> But HAL doesn't detect it at all. I use the generic ubuntu
> /usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi
>
> I suppose the problem is in the sequence :
> 1-autodetection of the USB serial adapter
> 2-autodetection of the serial tablet pluged on the adapter.
>
> I seen similar problems for other people in french ubuntu forum.
>
>
> Regards.
>
> Olivier
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Linuxwacom-devel mailing list
> Linuxwacom-devel@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

serial wacom tablet and HAL/PolicyKit

2009-11-14T14:34:44Z

Has anyone managed a serial wacom (pluged via an USB-serial adapter) to
autodetect HAL or Policykit ?
If anyone managed to have an autodetection by HAL or PolicyKit on a
direct USB plug, this could be helpfull too.

My USB WACOM is autodetected by hal (hotplug), but not my serial (on usb
adapter) one.

the adapter is well detected by the kernel, that's :
Prolific PL2303 USB to serial adaptor driver

a /dev/ttyUSB0 is created.

wacdump /dev/ttyUSB0 works well (on some retry, it doesn't work, I have
to deplug/replug the usb adapter from the pc).

It gives me on the model part :

MODEL=Wacom Intuos 9x12 ROM=1.1-7
CLS=Serial VNDR=Wacom DEV=Intuos SUB=GD-0912-R

But HAL doesn't detect it at all. I use the generic ubuntu
/usr/share/hal/fdi/policy/20thirdparty/10-linuxwacom.fdi

I suppose the problem is in the sequence :
1-autodetection of the USB serial adapter
2-autodetection of the serial tablet pluged on the adapter.

I seen similar problems for other people in french ubuntu forum.

Regards.

Olivier

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [Linuxwacom-discuss] 0.8.5 Problems - HAL and fdi.

2009-10-22T21:03:02Z

I thought you would look into it if you have the source :). Well, I'll get to it when I have time. Hope it will be before someone else.

Ping

On Thu, Oct 22, 2009 at 3:16 PM, Kory Prince <korylprince@...> wrote:

On Wed, 2009-10-21 at 15:53 -0700, Ping wrote:
> Do you have the xsetwacom source code from Ubunto? I think the issue
> maybe in xsetwacom.

I'll assume that means you wanted to look at it?

Using apt-get source, You can get the actual source the packages are
compiled from. Using that, it downloads ( or creates) three files.
Something called the orig.tar and the diff.tar. It then untars this to a
folder. (And I think applies the patches.)
I am uploading that folder it creates as I have no idea what to look
for...
Kory

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: getwacom.py

2009-10-21T08:41:32Z

http://linuxwacom.sourceforge.net/index.php/howto/install has been updated with the new link. Thank you Kory.

Ping

On Tue, Oct 20, 2009 at 6:12 PM, Kory Prince <korylprince@...> wrote:

Hi Ping!
Sorry it took so long to answer... I have been a bit busy.
The page looks great, but I did something that may help us both a lot.
I went ahead and created a sourceforge project for the script itself so
you I won't have to send you the new version everytime and you won't
have to change the link. Just change the link to the sourceforge page
for the script:
https://sourceforge.net/projects/getwacom/files/

Also, Just so you know, the script should work on non-debian systems.
Only one switch does not work, and the script handles this itself. Also
in the future I plan to add support for other systems. Thanks for all
your help!
Kory

On Wed, 2009-10-14 at 15:07 -0700, Ping wrote:
> Hi Kory,
>
> Your script is linked to
> http://linuxwacom.sourceforge.net/index.php/howto/install. Please
> take a look and let me know if it represents your original suggestion
> or not.
>
> Thank you so much on behalf of Debian-based users (if they allow me to
> do so :).
>
> Ping
>
> On Mon, Oct 12, 2009 at 4:34 PM, Kory Prince <korylprince@...>
> wrote:
> Hi Ping.
> I got my script to a place where I am willing to
> distribute it. I am
> attaching it.
> I would prefer that you upload it to your site, but if you
> want you can
> link to:
> http://www.theprinceonline.info/getwacom/getwacom.py
>
> (I'm just not sure about the long-term integrity of that
> link.)
>
> If you do post it to your site, you might want to make this
> note:
>
> At this time, getwacom.py doesn't support the --getbuilddeps
> option for
> non-Debian systems.
> If you have any questions, comments, or suggestions please
> email the
> author at korylprince [AT] gmail [DOTspam] com
>
> Thanks!
> Kory
>

Re: getwacom.py

2009-10-20T18:12:46Z

Hi Ping!
Sorry it took so long to answer... I have been a bit busy.
The page looks great, but I did something that may help us both a lot.
I went ahead and created a sourceforge project for the script itself so
you I won't have to send you the new version everytime and you won't
have to change the link. Just change the link to the sourceforge page
for the script:
https://sourceforge.net/projects/getwacom/files/

Also, Just so you know, the script should work on non-debian systems.
Only one switch does not work, and the script handles this itself. Also
in the future I plan to add support for other systems. Thanks for all
your help!
Kory

On Wed, 2009-10-14 at 15:07 -0700, Ping wrote:

> Hi Kory,
>
> Your script is linked to
> http://linuxwacom.sourceforge.net/index.php/howto/install. Please
> take a look and let me know if it represents your original suggestion
> or not.
>
> Thank you so much on behalf of Debian-based users (if they allow me to
> do so :).
>
> Ping
>
> On Mon, Oct 12, 2009 at 4:34 PM, Kory Prince <korylprince@...>
> wrote:
> Hi Ping.
> I got my script to a place where I am willing to
> distribute it. I am
> attaching it.
> I would prefer that you upload it to your site, but if you
> want you can
> link to:
> http://www.theprinceonline.info/getwacom/getwacom.py
>
> (I'm just not sure about the long-term integrity of that
> link.)
>
> If you do post it to your site, you might want to make this
> note:
>
> At this time, getwacom.py doesn't support the --getbuilddeps
> option for
> non-Debian systems.
> If you have any questions, comments, or suggestions please
> email the
> author at korylprince [AT] gmail [DOTspam] com
>
> Thanks!
> Kory
>

Re: getwacom.py

2009-10-14T15:07:57Z

Hi Kory,

Your script is linked to http://linuxwacom.sourceforge.net/index.php/howto/install. Please take a look and let me know if it represents your original suggestion or not.

Thank you so much on behalf of Debian-based users (if they allow me to do so :).

Ping

On Mon, Oct 12, 2009 at 4:34 PM, Kory Prince <korylprince@...> wrote:

Hi Ping.
I got my script to a place where I am willing to distribute it. I am
attaching it.
I would prefer that you upload it to your site, but if you want you can
link to:
http://www.theprinceonline.info/getwacom/getwacom.py

(I'm just not sure about the long-term integrity of that link.)

If you do post it to your site, you might want to make this note:

At this time, getwacom.py doesn't support the --getbuilddeps option for
non-Debian systems.
If you have any questions, comments, or suggestions please email the
author at korylprince [AT] gmail [DOTspam] com

Thanks!
Kory

getwacom.py

2009-10-12T16:34:18Z

Hi Ping.
I got my script to a place where I am willing to distribute it. I am
attaching it.
I would prefer that you upload it to your site, but if you want you can
link to:
http://www.theprinceonline.info/getwacom/getwacom.py

(I'm just not sure about the long-term integrity of that link.)

If you do post it to your site, you might want to make this note:

At this time, getwacom.py doesn't support the --getbuilddeps option for
non-Debian systems.
If you have any questions, comments, or suggestions please email the
author at korylprince [AT] gmail [DOTspam] com

Thanks!
Kory

[getwacom.py]

#!/usr/bin/python ########################################################## ## GetWacom ## ## Script to Download, Compile, and Install ## ## the latest Linux-Wacom Release ## ## Copyright 2009 Kory Prince <korylprince@...> ## ########################################################## # # # This program is free software; you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation; either version 2 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, # MA 02110-1301, USA. # Changelog: # 1.0 - First Version - 10/10/09 # 1.5 - Added directory option # Made hid-ids.h install much better # Major code cleanup - (varibles, True/False, etc) # Added --prefix option # Added User prompts with a --force-yes prompt. # Added many checks for options confliction # Added apt-get check # 10/12/09 import urllib2, re, os, getopt, sys def main(): """Main function that takes arguements from the command line.""" global wacompath, uname, force getbuilddeps, download, compilevar, install, wacompath, uname, prefix, force = False, False, False, False, os.getcwd(), os.uname()[2], "/usr", False try: opts, operands = getopt.getopt( sys.argv[1:], "dcghfi:", ["download=", "compile=", "install=", "getbuilddeps=", "help", "prefix=", "force-yes"] ) except getopt.GetoptError, err: print str(err) usage() sys.exit(2) for options in opts: if "--help" in options or "-h" in options: usage(helpstatus=True) sys.exit(2) #debug print opts, operands #Getting user-specified path if it exists if len(operands) > 1: print "You cannot specify more than one path." usage() sys.exit(2) if operands != []: wacompath = os.path.abspath(operands[0]) #Make sure the path is writable by the user perm = oct((os.stat(wacompath)[0]) & 0777) if ((int(perm[1]) > 5 ) and os.stat(wacompath)[4] == os.getuid()) or ((int(perm[2]) > 5) and os.stat(wacompath)[5] == os.getgid()) or (int(perm[3]) > 5): pass else: print wacompath + " is not writable!" sys.exit(1) print "##########" print "Using " + wacompath + " for download and compile path." for options in opts: #If using long name, true or false should be specified. if (options[0] == "--getbuilddeps"): if options[1].lower() == "true": getbuilddeps = True if (options[0] == "--download"): if options[1].lower() == "true": download = True if (options[0] == "--compile"): if options[1].lower() == "true": compilevar = True if (options[0] == "--install" or options[0] == "-i"): install = options[1].lower() if (options[0] == "--prefix"): prefix = options[1] if (options[0] == "--force-yes" or options[0] == "-y"): force = True #if using short name, it automates to true. if (options[0] == "-g"): getbuilddeps = True if (options[0] == "-d"): download = True if (options[0] == "-c"): compilevar = True print "We are about to:\nCheck the Latest Version of Linuxwacom" if getbuilddeps == True: print "Get Build Dependencies" if download == True: print "Download Latest Linuxwacom Package" if compilevar == True: if prefix != "/usr": print "Compile the Linuxwacom package with prefix " + prefix else: print "Compile the Linuxwacom package" if install != False and (install == "module" or install == "all"): print "Install the linuxwacom package as " + install if install == "module" or install == "all" and compilevar == False: print "WARNING: You have chosen to install without compiling. This will fail if you have not already compiled in " + wacompath shouldContinue() #We stick this here because there is no need to run it if the command exits improperly global wacomversion wacomversion = re.findall(r"(linuxwacom[\w\d\-\.][0-9-]\.[0-9\-]\.[0-9\-]+)", getLatestWacomUrl())[0] print "Latest Version: " + wacomversion if getbuilddeps == True: getBuildDeps() elif getbuilddeps == False: pass else: print "Option " + getbuilddeps + "is not a valid option for --getbuilddeps." usage() sys.exit(2) if download == True: getWacom() elif download == False: pass else: print "Option " + download + "is not a valid option for --download." usage() sys.exit(2) if compilevar == True: compileWacom(prefix) elif compilevar == False: pass else: print "Option " + compilevar + "is not a valid option for --download." usage() sys.exit(2) if install == "module" or install == "all": installWacom(install) elif install == False: pass else: print "Option " + install + "is not a valid option for --install." usage() sys.exit(2) print "All Done!" #################################################################################### # Done with main Function. # #################################################################################### def shouldContinue(): """Asks user if it should continue and waits for answer. Use --force-yes to skip.""" if force == True: return None answer = raw_input("Do you wish to continue? (Y/n):") yes = ("y", "Y", "yes", "YES", "") if answer in yes: pass else: print "Stopping." sys.exit(1) def usage(helpstatus=False): """Displays usage text. If helpstatus is true it displays the full text.""" if helpstatus == False: print """ Usage: getwacom.py [OPTION]... [download/compile path] OPTION takes the form of --OPTION[=option] Use 'getwacom.py --help' for more information.""" else: print """ Usage getwacom.py [OPTION]... [download/compile path] Download/compile path defaults to current directory unless specified. OPTION takes the form of --OPTION[=option] or -o Options do not need to be in any specific order. Available Options: (Defaults Capitalized.) --compile=true/FALSE Whether or not to compile -c release. --download=true/FALSE Whether or not to download -d latest linuxwacom release. --force-yes If enabled, prompts are -f skipped. --getbuilddeps=true/FALSE Whether or not to install -g build dependencies. --help Show this help message. -h --install=MODULE/all Whether or not to install. -i=MODULE/all Install as Module only, or the whole release. --prefix= Option to specify compile prefix. Default is /usr. Copyright Kory Prince 2009 - getwacom.py Version 1.5""" def parseAddress(address): """Takes an address and puts an 'http://' on it if not already there.""" if address[:7] != "http://": if address.find("://") != -1: print "Error: Cannot retrieve URL, protocol must be HTTP" sys.exit(1) else: address = "http://" + address return address def getWebsite(address): """Downloads address and puts returns the html""" fulladdress = parseAddress(address) try: website = urllib2.urlopen(fulladdress) except urllib2.HTTPError, e: print "Cannot retrieve URL: HTTP Error Code", e.code except urllib2.URLError, e: print "Cannot retrieve URL: " + e.reason[1] return website.read() def getLatestWacomUrl(): """parses the linuxwacom site and finds the newest version. Returns url for download.""" print "Checking for latest version..." html = getWebsite('http://linuxwacom.sourceforge.net/') #Sweet regex that finds any http(s) link with a bz2 file extension urlfind= r"(https?://+[\w\d:#@%/;$()~_?\+-=\\\.&]*bz2)" matchedurls = re.findall(urlfind,html) if matchedurls[0][-11] > matchedurls[1][-11]: return matchedurls[0] elif matchedurls[0][-11] < matchedurls[1][-11]: return matchedurls[1] else: if matchedurls[0][-9] > matchedurls[1][-9]: return matchedurls[0] elif matchedurls[0][-9] < matchedurls[1][-9]: return matchedurls[1] def getWacom(): """downloads and untars the latest wacom release""" url = getLatestWacomUrl() os.chdir(wacompath) print "Downloading Latest Release - " + wacomversion os.system("wget -m -nd " + url) print "Untarring package." os.system("tar xjvf " + wacomversion + ".tar.bz2") return None def getBuildDeps(): """Gets all the packages to compile linuxwacom""" aptexists = False for path in os.environ["PATH"].split(":"): if os.path.exists(path + "/apt-get"): aptexists = True if aptexists == False: print "--getbuilddeps currently only works on systems with apt-get installed! (Debian-based systems.)" sys.exit(1) print "Updating APT." shouldContinue() os.system("gksudo apt-get update") print "Installing required packages." os.system("sudo apt-get -y install build-essential libx11-dev libxi-dev x11proto-input-dev xserver-xorg-dev tk8.4-dev tcl8.4-dev libncurses5-dev linux-headers-"+(re.findall(r'([a-z]+)', uname)[0])) getHIDFile() def getHIDFile(): """Function to check if hid-ids.h file exists. If it does not then it is downloaded. Mainly for ubuntu Karmic.""" sourcefilepath = None print "Checking for hid-ids.h file." for location in ("/lib/modules/"+uname+"/source", "/lib/modules/"+uname+"/build", "/usr/src/linux /usr/src/linux-"+uname, "/usr/src/linux-2.6"): if os.path.exists(location + "/include/linux/input.h"): sourcefilepath = location break if sourcefilepath == None: print "Cannot find Header information. Make sure it is installed!" if os.path.exists(location + "/drivers/hid/hid-ids.h"): print "Found it! " + location + "/drivers/hid/hid-ids.h" else: print "File does not exist. Downloading from kernel.ubuntu.com." os.system("sudo wget -O " + location + "/drivers/hid/hid-ids.h http://kernel.ubuntu.com/git-repos/ubuntu/linux-2.6/drivers/hid/hid-ids.h") def compileWacom(prefix): """Compiles linuxwacom""" try: os.chdir(wacompath + "/" + wacomversion) except OSError: print "Cannot find linuxwacom path " + (wacompath + "/" + wacomversion) + ". Try running getwacom.py with --download=true." sys.exit(1) if prefix != "/usr": print "Preparing to compile with prefix " + prefix + "." else: print "Preparing to compile." shouldContinue() print "Configuring." os.system("./configure --enable-wacom --prefix=" + prefix) print "Compiling" os.system("make") os.chdir(wacompath) def installWacom(install="module"): """Installs linux wacom either as a module only or as all.""" try: os.chdir(wacompath + "/" + wacomversion) except OSError: print "Cannot find linuxwacom path " + (wacompath + "/" + wacomversion) + ". Try running getwacom.py with --download=true." sys.exit(1) print "Preparing to install as " + install + "." shouldContinue() if install == "all": print "Installing All." os.system("gksudo make install") else: print "Installing Module only." os.system("gksudo cp ./src/" + uname[0:6] + "/wacom.ko /lib/modules/" + uname + "/kernel/drivers/input/tablet/wacom.ko") os.chdir(wacompath) if __name__ == '__main__': main()

Re: Data from Wacom

2009-10-12T11:11:25Z

Elham -- if all you want to do is import something into
Matlab/mathematica, it might be in your best interest to draw your
picture into "inkskape" or some other vector drawing program, and then
export the resultant image. You wont' have to know how to code for this,

GI

On Mon, Oct 12, 2009 at 09:31:36AM -0700, Ping wrote:

> Hi Elham,
>
> I've replied to you last Wednesday. Those links are Wacom driver on Linux.
> If you need API and examples on other platforms, please check:
> http://www.wacomeng.com.
>
> On Linux, you can find examples and source code at the website. Please take
> a look at the following links:
>
> http://linuxwacom.sourceforge.net/index.php/appdev
> http://linuxwacom.sourceforge.net/index.php/overview
> http://linuxwacom.sourceforge.net/index.php/quantumtest
> http://linuxwacom.cvs.sourceforge.net/linuxwacom/
>
> Good luck.
>
> Ping
>
> On Sun, Oct 11, 2009 at 11:05 PM, Elham Chahardah Cheriki <
> elham.c.cheriki@...> wrote:
>
>> Dear Sir,
>>
>> I would like to ask you that if I want to get data from Wacom (X , Y , T,
>> P,angel ) and import to Matlab or Mathematic to see the curve 3D e.g(x,y,p)
>> how can I do it.
>>
>> I can see the data but I can not save it point by point in a txt file or
>> online import to Matlab or Mathematic.Could you send me the source code for
>> windows and linux if there exist?I am beginner in C and linux.
>>
>> I really need it .
>>
>>
>> Thanks in advance
>>
>> I am looking froward to hearing from you.
>>
>> Yours
>> Elham.C.Cheriki
>>

> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> Linuxwacom-devel mailing list
> Linuxwacom-devel@...
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

--
Seen on the back of a dirty car: washme.com

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

attachment0 (204 bytes) Download Attachment

Re: Data from Wacom

2009-10-12T09:31:36Z

Hi Elham,

I've replied to you last Wednesday. Those links are Wacom driver on Linux. If you need API and examples on other platforms, please check: http://www.wacomeng.com.

On Linux, you can find examples and source code at the website. Please take a look at the following links:

http://linuxwacom.sourceforge.net/index.php/appdev
http://linuxwacom.sourceforge.net/index.php/overview
http://linuxwacom.sourceforge.net/index.php/quantumtest
http://linuxwacom.cvs.sourceforge.net/linuxwacom/

Good luck.

Ping

On Sun, Oct 11, 2009 at 11:05 PM, Elham Chahardah Cheriki <elham.c.cheriki@...> wrote:

Dear Sir,

I would like to ask you that if I want to get data from Wacom (X , Y , T, P,angel ) and import to Matlab or Mathematic to see the curve 3D e.g(x,y,p) how can I do it.

I can see the data but I can not save it point by point in a txt file or online import to Matlab or Mathematic.Could you send me the source code for windows and linux if there exist?I am beginner in C and linux.

I really need it .

Thanks in advance

I am looking froward to hearing from you.

Yours
Elham.C.Cheriki

Data from Wacom

2009-10-11T23:05:18Z

Dear Sir,

I would like to ask you that if I want to get data from Wacom (X , Y , T, P,angel ) and import to Matlab or Mathematic to see the curve 3D e.g(x,y,p) how can I do it.

I can see the data but I can not save it point by point in a txt file or online import to Matlab or Mathematic.Could you send me the source code for windows and linux if there exist?I am beginner in C and linux.

I really need it .

Thanks in advance

I am looking froward to hearing from you.

Yours
Elham.C.Cheriki

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [PATCH] wcmTouch and wcmTPCButton should be distinct properties

2009-10-11T21:24:50Z

On Sun, Oct 11, 2009 at 7:59 PM, Peter Hutterer <peter.hutterer@...> wrote:

so with the examples you mentioned, Suppress and Threshold are related
enough that they could be grouped (if you want to). commonDBG definitely in
its own property (though I'm not a big fan of that property anyway, this
should be a DIX property).

I'm happy to apply the patches Tom sent, his explanations where enough to
convince me.

Great. Please commit Tom's (remove the part for wcmTouch).

Tom, do you have time (and interest) to take care of the other properties as well? You definitely have a better understand of the properties than I do. Thank you in advance.

> > Touch seems to (I don't actually have a device that supports touch) just
> > enable or disable touch events. So we might be able to kill the
> > property altogether and use the DEVICE_ENABLE control on the touch
> > device instead.
>
> How do we use the DEVICE_ENABLE control? Is it a generic property defined
> by evdev or other low level driver/module? Can we enable/disable at our
> wish from the driver? When we disable a device, do we just stop it from
> sending data to Xinput or something else? Sorry for asking you instead of
> searching for the answer myself. I am hoping to catch up with a shortcut.

DEVICE_ENABLE is a control provided by XI (XChangeDeviceControl), but since
server 1.6 we have a "Device Enabled" property that achieves the same
effect. so instead of wacom having its own property it's better to re-use
this property from the client-side tools.

you don't actually have to do anything special inside the driver to support
this property, if a client toggles it, the DEVICE_OFF/DEVICE_ON control proc
is called. If you need to toggle it from within the driver (I don't think
this is the case here?) you can use XIChangeDeviceProperty.

Yeah, I guess so. Ignore this one for now. I'll have to think about it when I get there to be sure. I am still dragged by xorg older than 1.6 and my own xsetwacom world. It will take a while for me to catch up.....

Ping

Re: [PATCH] wcmTouch and wcmTPCButton should be distinct properties

2009-10-11T19:59:05Z

On Sat, Oct 10, 2009 at 12:22:30PM -0700, Ping wrote:

> On Wed, Oct 7, 2009 at 11:55 PM, Thomas Jaeger <thjaeger@...> wrote:
>
> > On Wed, Oct 7, 2009 at 10:10 PM, Peter Hutterer <peter.hutterer@...>wrote:
> > > Sorry for the delay, bit flooded here.
> > > Is it necessary to split those two up? I named it "Extra buttons" because
> > I
> > > couldnt really think of something better but they seem connected enough
> > to
> > > justify a single property.
> > >
> > > As Ping said in the other email, properties don't need to be
> > human-readable
> > > beyond a certain extent and I'd like to avoid having dozens of
> > single-value
> > > properties that all enable or disable a feature. To me it seemed that
> > touch
> > > and TPCButton are both a kind of button so they go well together. I'm
> > happy
> > > to be convinced otherwise.
> > TPCButton isn't really a button, it rather controls when a button press
> > is sent: If the option is disabled the driver sends a click as soon as
> > the side switch is pressed, otherwise it is necessary to tap the pen to
> > get a click. This applies to all wacom devices, I think.
> >
>
> Tom is right. TPCButton can be applied to all tablet models (default to on
> for TabletPC's and off for all the others). It is a common option, i.e., it
> turns on/off for all tools that are associated with the same tablet. Due to
> its common feature, maybe we can group it with a few other common options
> (commonDBG, Suppress, Threshold? They don't belong together, I feel). So,
> Peter, do you have any rules/preference for grouping them together?

no hard rules, I'm just trying to group them as they make sense. If they
don't make sense in a group just split them up. There's nothing wrong with
having properties that only have a single value, I'm just trying to avoid
the case where we have too many properties that affect more or less the same
thing.

the closest thing I can come to a hard rule is that if you look at the list
of properties exported by a device, you should know immediately which
property the setting you want to change belongs to.

so with the examples you mentioned, Suppress and Threshold are related
enough that they could be grouped (if you want to). commonDBG definitely in
its own property (though I'm not a big fan of that property anyway, this
should be a DIX property).

I'm happy to apply the patches Tom sent, his explanations where enough to
convince me.

> > Touch seems to (I don't actually have a device that supports touch) just
> > enable or disable touch events. So we might be able to kill the
> > property altogether and use the DEVICE_ENABLE control on the touch
> > device instead.
>
> How do we use the DEVICE_ENABLE control? Is it a generic property defined
> by evdev or other low level driver/module? Can we enable/disable at our
> wish from the driver? When we disable a device, do we just stop it from
> sending data to Xinput or something else? Sorry for asking you instead of
> searching for the answer myself. I am hoping to catch up with a shortcut.

DEVICE_ENABLE is a control provided by XI (XChangeDeviceControl), but since
server 1.6 we have a "Device Enabled" property that achieves the same
effect. so instead of wacom having its own property it's better to re-use
this property from the client-side tools.

you don't actually have to do anything special inside the driver to support
this property, if a client toggles it, the DEVICE_OFF/DEVICE_ON control proc
is called. If you need to toggle it from within the driver (I don't think
this is the case here?) you can use XIChangeDeviceProperty.

Cheers,
Peter

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: Source Question

2009-10-11T11:18:55Z

It's not quite ready yet, and it needs some testing before I release it
to the world.
Once it is ready, you can put it on the site. It will be gplv2.
Kory

On Sun, 2009-10-11 at 10:40 -0700, Ping wrote:

> Hi Kory,
>
> I can post your script if you don't mind sending me a copy (and don't
> mind publicly sharing it). Or I can add a link at linuxwacom.sf.net to
> your page. Let me know which way you prefer.
>
> Ping
>
> On Sun, Oct 11, 2009 at 10:30 AM, Kory Prince <korylprince@...>
> wrote:
> Hi Ping,
> Thanks for the reply. I managed to cook up a python
> script that may
> solve my problem. It automatically parses the linuxwacom
> website and
> download the latest release (with options to compile and
> install as
> well.) As long as you don't dramatically change the format of
> the
> website, the script should work.
> If anyone wants a copy of the script, email me and I'll send
> it to you
> (it's still in development stages.)
> Thanks everyone!
> Kory
>
>
> On Fri, 2009-10-09 at 07:07 -0700, Ping wrote:
> > Hi Kory,
> >
> > Thank you for supporting linuxwacom project. I's say
> pointing to a
> > "hard-coded" version is not a good idea - we would like to
> recommand
> > them to the latest dash release since it normally fixes bugs
> for the
> > base version, especially Production release. Overwriting
> minor
> > releases is a commonly used method, especially in open
> source
> > community where updates occur often.
> >
> > It might be easier to direct your readers to
> linuxwacom.sf.net and let
> > them download the lastest (Production or Development)
> release. I know
> > one click solution is what you are trying to achieve. I feel
> lucky for
> > linuxwacom users on Ubuntu. You may want to create a website
> of your
> > own so you can take control of it?.....
> >
> > Ping
>
>
>

Re: Source Question

2009-10-11T10:40:16Z

Hi Kory,

I can post your script if you don't mind sending me a copy (and don't mind publicly sharing it). Or I can add a link at linuxwacom.sf.net to your page. Let me know which way you prefer.

Ping

On Sun, Oct 11, 2009 at 10:30 AM, Kory Prince <korylprince@...> wrote:

Hi Ping,
Thanks for the reply. I managed to cook up a python script that may
solve my problem. It automatically parses the linuxwacom website and
download the latest release (with options to compile and install as
well.) As long as you don't dramatically change the format of the
website, the script should work.
If anyone wants a copy of the script, email me and I'll send it to you
(it's still in development stages.)
Thanks everyone!
Kory

On Fri, 2009-10-09 at 07:07 -0700, Ping wrote:
> Hi Kory,
>
> Thank you for supporting linuxwacom project. I's say pointing to a
> "hard-coded" version is not a good idea - we would like to recommand
> them to the latest dash release since it normally fixes bugs for the
> base version, especially Production release. Overwriting minor
> releases is a commonly used method, especially in open source
> community where updates occur often.
>
> It might be easier to direct your readers to linuxwacom.sf.net and let
> them download the lastest (Production or Development) release. I know
> one click solution is what you are trying to achieve. I feel lucky for
> linuxwacom users on Ubuntu. You may want to create a website of your
> own so you can take control of it?.....
>
> Ping

Re: Source Question

2009-10-11T10:30:28Z

Hi Ping,
Thanks for the reply. I managed to cook up a python script that may
solve my problem. It automatically parses the linuxwacom website and
download the latest release (with options to compile and install as
well.) As long as you don't dramatically change the format of the
website, the script should work.
If anyone wants a copy of the script, email me and I'll send it to you
(it's still in development stages.)
Thanks everyone!
Kory

On Fri, 2009-10-09 at 07:07 -0700, Ping wrote:

> Hi Kory,
>
> Thank you for supporting linuxwacom project. I's say pointing to a
> "hard-coded" version is not a good idea - we would like to recommand
> them to the latest dash release since it normally fixes bugs for the
> base version, especially Production release. Overwriting minor
> releases is a commonly used method, especially in open source
> community where updates occur often.
>
> It might be easier to direct your readers to linuxwacom.sf.net and let
> them download the lastest (Production or Development) release. I know
> one click solution is what you are trying to achieve. I feel lucky for
> linuxwacom users on Ubuntu. You may want to create a website of your
> own so you can take control of it?.....
>
> Ping

Re: [PATCH] wcmTouch and wcmTPCButton should be distinct properties

2009-10-10T12:22:30Z

On Wed, Oct 7, 2009 at 11:55 PM, Thomas Jaeger <thjaeger@...> wrote:

On Wed, Oct 7, 2009 at 10:10 PM, Peter Hutterer <peter.hutterer@...> wrote:
> Sorry for the delay, bit flooded here.
> Is it necessary to split those two up? I named it "Extra buttons" because I
> couldnt really think of something better but they seem connected enough to
> justify a single property.
>
> As Ping said in the other email, properties don't need to be human-readable
> beyond a certain extent and I'd like to avoid having dozens of single-value
> properties that all enable or disable a feature. To me it seemed that touch
> and TPCButton are both a kind of button so they go well together. I'm happy
> to be convinced otherwise.
TPCButton isn't really a button, it rather controls when a button press
is sent: If the option is disabled the driver sends a click as soon as
the side switch is pressed, otherwise it is necessary to tap the pen to
get a click. This applies to all wacom devices, I think.

Tom is right. TPCButton can be applied to all tablet models (default to on for TabletPC's and off for all the others). It is a common option, i.e., it turns on/off for all tools that are associated with the same tablet. Due to its common feature, maybe we can group it with a few other common options (commonDBG, Suppress, Threshold? They don't belong together, I feel). So, Peter, do you have any rules/preference for grouping them together?

Touch seems to (I don't actually have a device that supports touch) just
enable or disable touch events. So we might be able to kill the
property altogether and use the DEVICE_ENABLE control on the touch
device instead.

How do we use the DEVICE_ENABLE control? Is it a generic property defined by evdev or other low level driver/module? Can we enable/disable at our wish from the driver? When we disable a device, do we just stop it from sending data to Xinput or something else? Sorry for asking you instead of searching for the answer myself. I am hoping to catch up with a shortcut.

Ping

Re: Source Question

2009-10-09T07:07:02Z

Hi Kory,

Thank you for supporting linuxwacom project. I's say pointing to a "hard-coded" version is not a good idea - we would like to recommand them to the latest dash release since it normally fixes bugs for the base version, especially Production release. Overwriting minor releases is a commonly used method, especially in open source community where updates occur often.

It might be easier to direct your readers to linuxwacom.sf.net and let them download the lastest (Production or Development) release. I know one click solution is what you are trying to achieve. I feel lucky for linuxwacom users on Ubuntu. You may want to create a website of your own so you can take control of it?.....

Ping

On Thu, Oct 8, 2009 at 2:49 PM, Kory Prince <korylprince@...> wrote:

I and another user, Favux, are some of the main upkeepers for wacom
tutorials on the ubuntu forums (Him more than I.)
We have been running into a problem. Everytime a new release for
linux-wacom comes out, all the old packages are deleted (as in
http://prdownloads.sourceforge.net/linuxwacom/linuxwacom-0.8.4-2.tar.bz2)

This causes problems since our tutorial just wgets the source. So
whenever you update, we have to fix the tutorial right away, or it won't
work.
I have noticed on the list that you are moving over to another
repository. Is there somewhere where all the packages are that we can
download from so that we won't have this problem every time linux-wacom
gets updated? Thanks!
Kory

Source Question

2009-10-08T14:49:53Z

I and another user, Favux, are some of the main upkeepers for wacom
tutorials on the ubuntu forums (Him more than I.)
We have been running into a problem. Everytime a new release for
linux-wacom comes out, all the old packages are deleted (as in
http://prdownloads.sourceforge.net/linuxwacom/linuxwacom-0.8.4-2.tar.bz2)

This causes problems since our tutorial just wgets the source. So
whenever you update, we have to fix the tutorial right away, or it won't
work.
I have noticed on the list that you are moving over to another
repository. Is there somewhere where all the packages are that we can
download from so that we won't have this problem every time linux-wacom
gets updated? Thanks!
Kory

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [PATCH] wcmTouch and wcmTPCButton should be distinct properties

2009-10-07T23:55:20Z

Peter Hutterer wrote:

> On Mon, Oct 05, 2009 at 12:39:44PM -0400, Thomas Jaeger wrote:
>> Thomas Jaeger wrote:
>>> This applies on top of the property-rework branch.
>> Sorry, forgot the attachment.
>
>> From b1b8c505b10619a08df703691f241162c353c845 Mon Sep 17 00:00:00 2001
>> From: Thomas Jaeger <ThJaeger@...>
>> Date: Mon, 5 Oct 2009 12:32:37 -0400
>> Subject: [PATCH] wcmTouch and wcmTPCButton should be distinct properties
>>
>> Expose wcmTouch as "Wacom Enable Touch" and !wcmTPCButton as
>> "Wacom Hover Click".
>
>
> Sorry for the delay, bit flooded here.
> Is it necessary to split those two up? I named it "Extra buttons" because I
> couldnt really think of something better but they seem connected enough to
> justify a single property.
>
> As Ping said in the other email, properties don't need to be human-readable
> beyond a certain extent and I'd like to avoid having dozens of single-value
> properties that all enable or disable a feature. To me it seemed that touch
> and TPCButton are both a kind of button so they go well together. I'm happy
> to be convinced otherwise.

TPCButton isn't really a button, it rather controls when a button press
is sent: If the option is disabled the driver sends a click as soon as
the side switch is pressed, otherwise it is necessary to tap the pen to
get a click. This applies to all wacom devices, I think.

Touch seems to (I don't actually have a device that supports touch) just
enable or disable touch events. So we might be able to kill the
property altogether and use the DEVICE_ENABLE control on the touch
device instead.

Tom

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@...
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Re: [PATCH] wcmTouch and wcmTPCButton should be distinct properties

2009-10-07T22:10:51Z

On Mon, Oct 05, 2009 at 12:39:44PM -0400, Thomas Jaeger wrote:
> Thomas Jaeger wrote:
> > This applies on top of the property-rework branch.
>
> Sorry, forgot the attachment.

> From b1b8c505b10619a08df703691f241162c353c845 Mon Sep 17 00:00:00 2001
> From: Thomas Jaeger <ThJaeger@...>
> Date: Mon, 5 Oct 2009 12:32:37 -0400
> Subject: [PATCH] wcmTouch and wcmTPCButton should be distinct properties
>
> Expose wcmTouch as "Wacom Enable Touch" and !wcmTPCButton as
> "Wacom Hover Click".

Sorry for the delay, bit flooded here.
Is it necessary to split those two up? I named it "Extra buttons" because I
couldnt really think of something better but they seem connected enough to
justify a single property.

As Ping said in the other email, properties don't need to be human-readable
beyond a certain extent and I'd like to avoid having dozens of single-value
properties that all enable or disable a feature. To me it seemed that touch
and TPCButton are both a kind of button so they go well together. I'm happy
to be convinced otherwise.

Cheers,
Peter

> ---
> src/wcmXCommand.c | 36 ++++++++++++++++++++----------------
> 1 files changed, 20 insertions(+), 16 deletions(-)
>
> diff --git a/src/wcmXCommand.c b/src/wcmXCommand.c
> index 756c1e7..189a7fa 100644
> --- a/src/wcmXCommand.c
> +++ b/src/wcmXCommand.c
> @@ -395,7 +395,8 @@ Atom prop_cursorprox;
> Atom prop_capacity;
> Atom prop_threshold;
> Atom prop_suppress;
> -Atom prop_extrabuttons;
> +Atom prop_touch;
> +Atom prop_hover;
>
> static Atom InitWcmAtom(DeviceIntPtr dev, char *name, int format, int nvalues, int *values)
> {
> @@ -494,10 +495,11 @@ void InitWcmDeviceProperties(LocalDevicePtr local)
> values[1] = common->wcmRawSample;
> prop_suppress = InitWcmAtom(local->dev, "Wacom Sample and Suppress", 32, 2, values);
>
> - values[0] = common->wcmTPCButton;
> - values[1] = common->wcmTouch;
> - prop_extrabuttons = InitWcmAtom(local->dev, "Wacom Extra Buttons", 8, 2, values);
> + values[0] = common->wcmTouch;
> + prop_touch = InitWcmAtom(local->dev, "Wacom Enable Touch", 8, 1, values);
>
> + values[0] = !common->wcmTPCButton;
> + prop_hover = InitWcmAtom(local->dev, "Wacom Hover Click", 8, 1, values);
> }
>
> int xf86WcmSetProperty(DeviceIntPtr dev, Atom property, XIPropertyValuePtr prop,
> @@ -716,28 +718,30 @@ int xf86WcmSetProperty(DeviceIntPtr dev, Atom property, XIPropertyValuePtr prop,
>
> if (!checkonly && common->wcmThreshold != value)
> common->wcmThreshold = value;
> - } else if (property == prop_extrabuttons)
> + } else if (property == prop_touch)
> {
> CARD8 *values = (CARD8*)prop->data;
>
> - if (prop->size != 2 || prop->format != 8)
> + if (prop->size != 1 || prop->format != 8)
> return BadValue;
>
> - /* TCPButton */
> if ((values[0] != 0) && (values[0] != 1))
> return BadValue;
>
> - /* TOUCH */
> - if ((values[1] != 0) && (values[1] != 1))
> + if (!checkonly && common->wcmTouch != values[1])
> + common->wcmTouch = values[1];
> + } else if (property == prop_hover)
> + {
> + CARD8 *values = (CARD8*)prop->data;
> +
> + if (prop->size != 1 || prop->format != 8)
> return BadValue;
>
> - if (!checkonly)
> - {
> - if (common->wcmTPCButton != values[0])
> - common->wcmTPCButton = values[0];
> - if (common->wcmTouch != values[1])
> - common->wcmTouch = values[1];
> - }
> + if ((values[0] != 0) && (values[0] != 1))
> + return BadValue;
> +
> + if (!checkonly && common->wcmTPCButton != !values[0])
> + common->wcmTPCButton = !values[0];
> }
>
> return Success;
> --
> 1.6.3.3

Farewell

2009-10-07T02:16:18Z

Currents Express


		October 7, 2009 Volume 7, Number 19

Volume 7, Number 19 | (c) 2009 Coastal Technologies Corp.
500 Studio Drive | Virginia Beach, VA 23452

Click here to visit our blog!

This email was sent to linuxwacom-devel@... because of your business relationship with Coastal Technologies.

Coastal does not sell or rent your email address to third parties. Privacy Policy

Forward to a Friend

Did you receive this email from a friend or colleague? Subscribe to the Coastal Safety & Environmental email list.

Update Preferences or Change Email Format

Unsubscribe from all Coastal Technologies email lists.