Oh, sorry. It turned out the device does not disappear from xinput but,
for an unknown reason, starts off as floating. After reattaching it, I
get the expected results. Sorry for the noise.
On Sun, Jul 08, 2012 at 01:32:15AM +0200, Cedric Sodhi wrote:
> Wacom used to work for the more-or-less
Wacom used to work for the more-or-less HID compliant egalax 0eef:a001,
but when I try it these days, by using the "wacom" X.org driver, I get
no responses whatsoever.
With evdev, the egalax still shows up in "xinput list". When I use
wacom, however, the driver logs that:
(II) Using input driver
Hello everyone,
this Mail is primarily directed at Peter or anyone who has an opinion on
that.You said on xorg-devel that a mechanism for precedence between,
say, mouse and pen, pen and touch, etc. should not reside in the X input
layer but instead run as a userspace daemon. While I generally get
On Mon, Jun 04, 2012 at 09:58:27AM +1000, Peter Hutterer wrote:
> On Thu, May 31, 2012 at 08:02:18PM +0200, Cedric Sodhi wrote:
> > Hello,
> >
> > now there ais all kind of multiness involved with wacom,
> >
> > Multitouch (as in, well, multitouch),
> >
&g
Hello,
now there ais all kind of multiness involved with wacom,
Multitouch (as in, well, multitouch),
Multiple Pointers (as in, one or more pointers from the touchscreen,
others from the digizizer, ...)
Multiple Devices (as in, touchscreen, digitizer, yet another
touchscreen, ...)
all of which
On Sat, Jan 21, 2012 at 06:15:35PM -0600, Chris Bagwell wrote:
> On Sat, Jan 21, 2012 at 2:31 PM, Cedric Sodhi wrote:
> > On Sat, Jan 21, 2012 at 11:14:37PM +0700, Alexey Osipov wrote:
> >> Okay, I think I see the problem.
> >>
> >> You have a touch
d not make no heads nor
tail of that. There was no enum, whatsoever, identifying the settings.
Only strings. Bizarre.
>
> Alexey.
>
> В Сбт, 21/01/2012 в 16:39 +0100, Cedric Sodhi пишет:
> > Alexey, here is some info, as I said with current master:
> >
> > $
I would like to discuss the topic of precedence. Currently, XF86/I/W
manages multiple "subdevices" of a single device internally.
That solution does not seem very good for the long term.
Ben Tissoires once told me about a vision in which all these problems
should be rectified, somewhere, somehow,
t looking for how to implement xinput
properties? Once I figured that out I may actually produce useful
patches.
> So, if you are hacking sources anyway, you may try to remove WCM_LCD
> flag from your device and see if it helps.
>
> Alexey.
>
> В Сбт, 21/01/2012 в 16
On Sat, Jan 21, 2012 at 10:00:41AM -0600, Favux ... wrote:
> Cedric, are you talking about your ASUS EEE Slate with the Wacom
> digitizer and eGalax touchscreen?
>
> Last I saw Chris was saying use evdev not xf86-input-wacom?
I have no memory of that. The xf86-input-wacom works fine with any
gen
that didn't make a difference though.
Why should it. That behaviour we are talking about really has nothing at
all to do with gestures.
What do you mean you have never seen such behaviour even before your
patches?! What I described is the normal behaviour! What did you
understand?
Cedric
On Sa
I just cloned xf86-input-wacom and compiled and I notice no difference
other than my local patch (which give pens a global precedence over ANY
touch, which I need because my touch-device is not the same as the pen
device) rendering it unusuable.
Without that patch, the mouse pointer still drags wh
Hi Alexey, thanks for the enhacement. Althought I think it would surely
be nicer if this was generically possible regardless of the device type,
I only want it for the touchpad.
On Sat, Jan 21, 2012 at 10:01:09PM +0700, Alexey Osipov wrote:
> Hi, guys.
>
> Note that my patches only applicable to
Forgive my ignorance, but if this is, as you claim, the default
behaviour as of 0.13.0, how would I get the "legacy" behaviour that I
currently experience in 0.12.0. That is "traditional touchscreen
behaviour" where the button is pressed when the finger is touched?
Trying 0.13 straight away, thank
I don't understand what you are saying. My question was whether the
wacom can emulate the behaviour of a touchpad, that is, not going
"Button Press" when I touch the device (well, you know how a touchpad
behaves).
You describe the behaviour that I would like to have, but do not explain
how to make
Does linuxwacom support a touchpad-like mode? That is, only "tapping"
creates a click while physically dragging only moves the mouse pointer.
--
Try before you buy = See our experts in action!
The most comprehensive online
t was
previously attempted and is also not supported by QT.
So I guess I'm stuck without MT for now.
Thanks everyone.
On Thu, Jan 05, 2012 at 10:24:15AM +0100, Cedric Sodhi wrote:
> On Wed, Jan 04, 2012 at 09:50:31PM -0600, Chris Bagwell wrote:
> > On Wed, Jan 4, 2012 at 4:34 PM,
On Wed, Jan 04, 2012 at 09:50:31PM -0600, Chris Bagwell wrote:
> On Wed, Jan 4, 2012 at 4:34 PM, Cedric Sodhi wrote:
> > Hello everyone,
> >
> > I hope you can shed a little light on this, multitouch is a complete
> > mystery to me. I know that my eGalax is ru
Hello everyone,
I hope you can shed a little light on this, multitouch is a complete
mystery to me. I know that my eGalax is running fine with the
hid-multitouch these days but I'm completely irritated as for what is
required to actually get multitouch support in X.
I didn't need it so far, but a
> > >> You'll only get them for devices handled by HID drivers. On my
> > >> tablet, thats only 1 touchscreen. I was in fact assuming you only
> > >> have 1 HID device.
> > >
> > > The other one is my bluetooth keyboard.
> > >>
> > >> Can you retry this and do the exact filename? Also, you will n
On Fri, Nov 18, 2011 at 08:58:29AM -0600, Chris Bagwell wrote:
> On Fri, Nov 18, 2011 at 8:22 AM, Cedric Sodhi wrote:
> > Hello, do you have an idea how to decrease the sensitivity? Currently, a
> > touch is already registered before I even touch the screen.
>
> Are you ta
Hello, do you have an idea how to decrease the sensitivity? Currently, a
touch is already registered before I even touch the screen.
--
All the data continuously generated in your IT infrastructure
contains a definitive r
On Thu, Nov 17, 2011 at 06:26:04PM -0600, Chris Bagwell wrote:
> On Thu, Nov 17, 2011 at 3:54 AM, Cedric Sodhi wrote:
> >> > > I updated to GIT and it appears that the wacom now works both, clicks
> >> > > and absolute mode correctly. On the other hand, the
On Thu, Nov 17, 2011 at 10:10:49AM +0100, Cedric Sodhi wrote:
> On Thu, Nov 17, 2011 at 10:01:11AM +0100, Cedric Sodhi wrote:
> > On Thu, Nov 17, 2011 at 09:01:07AM +0100, Cedric Sodhi wrote:
> > > On Thu, Nov 17, 2011 at 08:37:05AM +0100, Cedric Sodhi wrote:
> > > >
On Thu, Nov 17, 2011 at 10:01:11AM +0100, Cedric Sodhi wrote:
> On Thu, Nov 17, 2011 at 09:01:07AM +0100, Cedric Sodhi wrote:
> > On Thu, Nov 17, 2011 at 08:37:05AM +0100, Cedric Sodhi wrote:
> > > On Thu, Nov 17, 2011 at 08:30:32AM +0100, Cedric Sodhi wrote:
> > > &
On Thu, Nov 17, 2011 at 09:01:07AM +0100, Cedric Sodhi wrote:
> On Thu, Nov 17, 2011 at 08:37:05AM +0100, Cedric Sodhi wrote:
> > On Thu, Nov 17, 2011 at 08:30:32AM +0100, Cedric Sodhi wrote:
> > > I've got even further good news to report. Although they kind of
> > &g
On Thu, Nov 17, 2011 at 08:37:05AM +0100, Cedric Sodhi wrote:
> On Thu, Nov 17, 2011 at 08:30:32AM +0100, Cedric Sodhi wrote:
> > I've got even further good news to report. Although they kind of
> > question the relation between xinput and xsetwacom again. That is:
> >
On Thu, Nov 17, 2011 at 08:30:32AM +0100, Cedric Sodhi wrote:
> I've got even further good news to report. Although they kind of
> question the relation between xinput and xsetwacom again. That is:
>
> I said that the eGalax, if using the Wacom driver, behaves in "Rela
I've got even further good news to report. Although they kind of
question the relation between xinput and xsetwacom again. That is:
I said that the eGalax, if using the Wacom driver, behaves in "Relative"
Mode, although xsetwacom claims it was "Absolute". Using xsetwacom could
not change this, but
like
> ALWAYS_VALID is indeed the key to this.
>
> Chris
>
> On Wed, Nov 16, 2011 at 2:48 PM, Cedric Sodhi wrote:
> > Dear Benjamin,
> >
> > I applied your patch tp 3.2-jikos (uname shows 3.1, though). The
> > diff to jikos' original is now [attach
t values.
The log which I attached to my last email was the one I took after
making the changes to the code. I forgot to specify that.
Cedric
> Cheers,
> Benjamin
>
>
> On Wed, Nov 16, 2011 at 21:48, Cedric Sodhi wrote:
> > Dear Benjamin,
> >
> > I applied you
Dear Benjamin,
I applied your patch tp 3.2-jikos (uname shows 3.1, though). The
diff to jikos' original is now [attached].
Chris says the output of evtest still signifies problems with
multitouch:
> > http://ompldr.org/iYmIzYw
>
> Cedric, can you send these logs to Benjamin for ideas? The HID e
Hello, I can report quite a bit of good news now:
One: Cleanly applying the required quirks and not blindly copying those
of the other DWAV devices as I did it when adding the ID to hid-ids.h
solves the jamming of the clicks and results in a perfectly well working
device, with evdev, that is.
Two
On Mon, Nov 14, 2011 at 12:22:54PM -0600, Chris Bagwell wrote:
> On Mon, Nov 14, 2011 at 1:13 AM, Cedric Sodhi wrote:
> > On Sun, Nov 13, 2011 at 05:11:46PM -0600, Chris Bagwell wrote:
> >> >
> >> >>
> >> >> I also find using the kernel hid d
PS: If you want that awesome script of mine, you can buy it for $2 per
license.
(it appears to become quite a habit of me to forget the attachments,
sorry)
On Tue, Nov 15, 2011 at 08:04:05PM +0100, Cedric Sodhi wrote:
> Hello everyone,
>
> until we have multi-point calibration, I
Hello everyone,
until we have multi-point calibration, I think the calibration could be
made a bit more intuive from a user's perspective. I wrote a little
script which demonstrates how I think a user would like to calibrate the
tablet. Specifying Maximum and Minimum values might be convenient for
On Sun, Nov 13, 2011 at 05:11:46PM -0600, Chris Bagwell wrote:
> On Sun, Nov 13, 2011 at 10:16 AM, Cedric Sodhi wrote:
> > On Sun, Nov 13, 2011 at 09:21:20AM -0600, Chris Bagwell wrote:
> >> On Sat, Nov 12, 2011 at 9:42 AM, Cedric Sodhi wrote:
> >> > Chris, I jus
On Sun, Nov 13, 2011 at 09:21:20AM -0600, Chris Bagwell wrote:
> On Sat, Nov 12, 2011 at 9:42 AM, Cedric Sodhi wrote:
> > Chris, I just compiled from Torvalds' HEAD (adding MULTITOUCH5 as usual)
> > and the clicking still jams.
> >
>
> Hmm, I just tried that
Thanks Chris:
I don't have much to offer for your specific questions other than you
should be able to determine behavior by looking at output of
isdv4-serial-debugger.
One other thing to try. How does the stylus track when using windows?
I had a touchscreen (no stylus) once that its behaviour
An apology in advance for my poor conduct with the list. I don't know
how to properly reply to a thread of which I have no mails in my inbox,
so I just copied the threadtitle from the archives. Sorry if it ends up
creating a new thread.
Chris, I just compiled from Torvalds' HEAD (adding MULTITOUCH
Hello everybody,
are there any intentions or just the possibility to calibrate Wacoms
with n-point (n+1-th order) maps? I assume there is a good reason why so
far we only have 1st-order/2-point mappings? I think this is a point
which matters for all those tablet users out there, like I am one.
As
Hello, I wanted to ask you a specific question concerning the ISDv4, if
someone of you happend not to be on the discuss list. That is, wether
the device actually reports values beyond its normal edges.
As I described, near the edges, the cursor deviates towards theses
edges, when calibrated to "0
On Tue, Nov 01, 2011 at 01:01:22PM -0500, Chris Bagwell wrote:
> On Tue, Nov 1, 2011 at 12:44 PM, Cedric Sodhi wrote:
> > Hello,
> >
> > unfortunally, I still have trouble with the touchpad. Clicking it
> > doesn't appear to work correctly. I think this is a
e in man pages; similar to how "man synaptics" does it.
>
> Patches welcome (since this is on the developers list)!
>
> Chris
>
> On Wed, Nov 2, 2011 at 8:50 AM, Cedric Sodhi wrote:
> > Well, this is interesting. I found the solution which is rather easy,
> >
Is it that some settings can only be set by xinput cli and
others only by xsetwacon cli? Sounds a little strange to me - I would
rather expect all settings to be handled by xsetwacom (I would even
prefer if all settings were handled by xinput).
On Wed, Nov 02, 2011 at 11:52:59AM +0100, Cedric S
Hello, the device is a 056a:0090 n USB. I'm 99.99% certain that the
button on the side of my stylus used to work, but it no longer does. GPM
and the event interface still respond to the button (GPM pastes, when I
press it, which means it is reported as the right button), but there is
no response to
On Tue, Nov 01, 2011 at 06:44:08PM +0100, Cedric Sodhi wrote:
> Hello,
>
> unfortunally, I still have trouble with the touchpad. Clicking it
> doesn't appear to work correctly. I think this is a bug on the kernel
> side (hid-multitouch) of things because it doesn't wor
Hello,
unfortunally, I still have trouble with the touchpad. Clicking it
doesn't appear to work correctly. I think this is a bug on the kernel
side (hid-multitouch) of things because it doesn't work in GPM either.
In X11 it appears to be "always clicked". From boot on and starting X:
Everything
> > Darn. I guess that would have been to easy. I've note added an ID
> > yet to hid-multitouch so I may have got it wrong. I'll see if I can
> > find more info.
>
> OK, found out what I missed. When you have a driver that is
> auto-grabbed by generic-usb then you need to add it to a generic-u
On Thu, Oct 27, 2011 at 11:36:43AM -0500, Chris Bagwell wrote:
> Linux tends to require white lists for supported touchscreens. So it
> doesn't matter what drivers you compile it... its OK to compile them
> ALL in and let whichever says it owns that product ID to claim it.
>
> > [ 3.226217] us
On Thu, Oct 27, 2011 at 10:31:32AM -0500, Chris Bagwell wrote:
> On Thu, Oct 27, 2011 at 10:01 AM, Cedric Sodhi wrote:
> > Kernel Config I:
> >
> > HID_MULTITOUCH=M
> > USB_HIDDEV=Y
> > TOUCHSCREEN_USB_COMPOSITE=N
> >
> > I do have three mice input
Thanks Chris for replying, I knew I could rely on you guys :)
On Thu, Oct 27, 2011 at 09:07:37AM -0500, Chris Bagwell wrote:
> On Thu, Oct 27, 2011 at 7:25 AM, Cedric Sodhi wrote:
> > I recently bought an ASUS EEE Slate which has a eGalax Touchpad and a
> > WACOM Digitizer (Styl
I recently bought an ASUS EEE Slate which has a eGalax Touchpad and a
WACOM Digitizer (Stylus & Erasor). I did not know that. I thought it was
all WACOM, now I'm faced with the prolem that I have no driver for the
eGalax touchpad, I hope you can help, since I don't know any other
people on the inte
icial, but they should narrow
> down if the problem is related to the number of touch points being
> detected by the tablet.
>
> Jason
>
> ---
> Day xee-nee-svsh duu-'ushtlh-ts'it;
> nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it.
> Huu-chan xuu na
ize these tests are pretty artificial, but they should narrow
> down if the problem is related to the number of touch points being
> detected by the tablet.
>
> Jason
>
> ---
> Day xee-nee-svsh duu-'ushtlh-ts'it;
> nuu-wee-ya' duu-xan' 'vm-nvshtlh-t
Is there anybody working on the touchpad at all? It's been at least two
weeks since I filed those bugs on the touchpad and there is no reply
neither on the list nor on the tracker whatsoever? Is touchpad
development not going on?
.
Any feedback?!
On Sat, May 07, 2011 at 09:56:34PM +0200, Cedric Sodhi wrote:
> I'd like to suggest that
>
> * A half Click (Button 1 Press) is only emitted if the finger is touched and
> pulled (as for dragging)
>
> * A complete click is only performed /aft
Can anyone preproduce it?
On Sat, May 07, 2011 at 09:39:39PM +0200, Cedric Sodhi wrote:
> Sorry, lost all emails from the previous thread, so I hope you don't
> mind if I start that over, with a new starting point:
>
>
> The "Pen takes precedence over touch" t
I'd like to suggest that
* A half Click (Button 1 Press) is only emitted if the finger is touched and
pulled (as for dragging)
* A complete click is only performed /after/ the finger has been
retracted from the touchscreen
This would allow for less interference between clicking and gestures
Sorry, lost all emails from the previous thread, so I hope you don't
mind if I start that over, with a new starting point:
The "Pen takes precedence over touch" thing works in 70% of the cases,
I'd say. The other 30% are those where I rest my palm on the screen.
In those cases, which are with 95
that touchpad that made the cursor jump.
Sorry for having pointed you in the wrong direction.
Cedric
On Wed, May 04, 2011 at 08:42:20AM -0500, Chris Bagwell wrote:
> On Wed, May 4, 2011 at 8:22 AM, Cedric Sodhi wrote:
> >
> > On Tue, May 03, 2011 at 12:27:50PM -0500, Chris Bagwell
After a bit of experimenting I found the solution. The touchpads
currents appeared to interfere with the touchscreen capacitors. So
turning the touchpad of with the "synclient TouchPadOff=1" command
resolved that.
On Wed, May 04, 2011 at 11:43:56PM +0200, Cedric Sodhi wrote:
> I su
I suspect this is a H/W issue but you can never be sure (I already asked
on the HP forums though and if nothing helps I'll send the notebook in).
My problem is that the cursor is sometimes shaking badly, and when I
move the computer it starts jumping arround. I don't know how to clearly
reproduce
You can't right click without leftclicking either.
On Mon, May 02, 2011 at 10:44:55AM -0500, Favux ... wrote:
> If you have Ubuntu Natty (11.04) or the equivalent (Xserver 1.10,
> kernel 2.6.37 or 38) you can place your BambooPT touch on the Synaptic
> driver if you prefer.
>
> Favux
>
> ---
A hint at least? The touchscreen is really problematic and I wonder
whether I should have a settable capacity
On Tue, May 03, 2011 at 06:57:18PM +0200, Cedric Sodhi wrote:
> This is bizarre. I think it musn't be the touchscreen but it's the
> driver itsself: Example: I set a cli
On Tue, May 03, 2011 at 12:27:50PM -0500, Chris Bagwell wrote:
> On Tue, May 3, 2011 at 3:03 AM, Cedric Sodhi wrote:
> > On Tue, May 03, 2011 at 03:08:09PM +1000, Peter Hutterer wrote:
> >> On Mon, May 02, 2011 at 05:31:23PM +0200, Cedric Sodhi wrote:
> >> > H
en rotates again. That cant be a hardware issue since I haven't even
touched the corner in which the rotate-button is!!!
On Tue, May 03, 2011 at 06:03:32PM +0200, Cedric Sodhi wrote:
> Do you have any idea how to reduce the sensitivity just a little bit?
> Using a different driver maybe?
Do you have any idea how to reduce the sensitivity just a little bit?
Using a different driver maybe?
On Mon, May 02, 2011 at 06:08:05PM +0200, Cedric Sodhi wrote:
> I think this is a bug:
>
> With aforementioned device, 39-rc5 kernel and GIT driver, the
> touchscreen is borderlin
On Tue, May 03, 2011 at 03:08:09PM +1000, Peter Hutterer wrote:
> On Mon, May 02, 2011 at 05:31:23PM +0200, Cedric Sodhi wrote:
> > Hello, I only built the regular TABLET_USB_WACOM and installed the
> > regular xf86-input-wacom from GIT. And I guess the one you meantioned is
>
It's not a Bamboo. It's a ISDV4 serial wacom :-/
On Mon, May 02, 2011 at 10:44:55AM -0500, Favux ... wrote:
> If you have Ubuntu Natty (11.04) or the equivalent (Xserver 1.10,
> kernel 2.6.37 or 38) you can place your BambooPT touch on the Synaptic
> driver if you prefer.
>
> Favux
>
> -
I think this is a bug:
With aforementioned device, 39-rc5 kernel and GIT driver, the
touchscreen is borderline-capacitive. Even the mere history of a finger
having touched the screen will sometimes randomly make it click.
When I look at xsetwacom the Capacity Setting is set to -1. I think this
is
Hello again,
Gestures for touchscreens is a great achievement, I ran into one little
problem though and I wonder whether it can be solved from the logical
point. That is, if I want to scroll by a two-finger gesture, I
necessarily start by touching down with one finger and that already
counts as a
s did not.
>
> Also, recently some logic was added to xf86-input-wacom for case of a
> 2nd Linux kernel touchscreen driver and give priority to pen&eraser.
>
> So that leaves 1 or 2 drivers left that need to address this issue.
>
> Chris
>
> On Mon, May 2, 2011 at
I do have a capacitive touchscreen with Wacom support. I notice that
whatever is caught first, hand or pen, will take precedence over the
other. Is there a way to always give the stylus || eraser precedence
over the capacitive touch?
kind regards,
ManDay
PS: Thanks to whoever responded to my ques
Hello,
Wacom devices are mapped to /dev/input/event and ./mouce devices by udev.
Contrary to the X-org wacom driver which goes
THROUGH those event devices, GPM reads the data from the devices directly.
So I wonder: How do I configure the driver "one level below X".
thinking about it, I wonder
ot; so that the pad maps to my laptop-screen when
only that screen is on, I get a proper mapping.
But when I set the same "Area " when an external Monitor is
activated the mapping changes.
On Thu, Mar 24, 2011 at 12:57:37PM -0700, Jason Gerecke wrote:
> On Thu, Mar 24, 2011 at 12:29 PM
Hello, I find it rather inconvenient that the Area Option (rather recent
GIT) appears to depend on the output device and is relative to the
screen area.
Meaning that the same Area Options have different effects when I use two
different screen setups.
Is there a particular reason why that is the ca
t
> devices? Like the early days of HAL before wacom-to-hal. I'm pretty
> sure that's been addressed upstream. Peter gave an example snippet
> for a dependent device a while ago. He can tell us when to expect it.
> I actually thought it might be in 1.9.
>
> In the
ettings to xorg apart from
manually xauthing and using xset/xinput to do that.
If you know how udev (possibly to custom attributes) can configure xorg
please explain it!
On Wed, Jan 26, 2011 at 03:53:05PM +1000, Peter Hutterer wrote:
> On Tue, Jan 25, 2011 at 09:06:18PM +0100, Cedric Sodhi wro
Hello, this is the same for all devices, I think. At least it's the same
for my Intuos4. But I think that's okay.
It's not the responsibility of the driver to re-initialize the device
with the old settings - the driver is simply the method to communicate
with it, it shall not offer any "special se
Hello,
I'd like to address the issue of LEDs in this separate thread. The
solution that is provided by Christoph Karg's utility is a great step
forward, given that we can now use the OLEDs at all, but it's also in
several areas problematic:
-> The utility interferes with the kernel driver, requir
On Mon, Jan 10, 2011 at 09:16:14AM +1000, Peter Hutterer wrote:
> On Sat, Jan 08, 2011 at 11:51:41AM +0100, Cedric Sodhi wrote:
> > I'm curious whether it would be possible and make sense to implement the
> > mode in which the pen could be read out so that it's prox
he has posted it yet.
>
> Favux
>
> On Sun, Jan 9, 2011 at 5:01 PM, Peter Hutterer
> wrote:
> > On Sun, Jan 09, 2011 at 06:13:42PM +0100, Cedric Sodhi wrote:
> >> Hi, this is a "wish" i had for the driver that I'd consider very useful.
> >> I&
On Sun, Jan 09, 2011 at 11:26:05AM -0600, Chris Bagwell wrote:
> On Sun, Jan 9, 2011 at 11:13 AM, Cedric Sodhi wrote:
> > Hi, this is a "wish" i had for the driver that I'd consider very useful.
> > I've recently written a simple bash script which scripts the
Hi, this is a "wish" i had for the driver that I'd consider very useful.
I've recently written a simple bash script which scripts the
functionality of the button, an example the button on the wheel changes
which keycodes the wheel sumit and hence which function in cotrnols.
If anyone is interested
I'm curious whether it would be possible and make sense to implement the
mode in which the pen could be read out so that it's proximity value
(which is currently in no way getting anywhere beyond the driver) is
mapped to pressure (and pressure doesnt matter).
One of the buttons could enable "sprayi
Looks like my observation wasn't fully correct. The bindings to in fact
work (I must have been confued by Rel/Abs) its just --get that doesnt
display the right data
--
Learn how Oracle Real Application Clusters (RAC) One N
The same happens for StripLUp etc. By the way: Although the RelWUp etc.
entries appear to be put into some desastrous state the pad still emits
Button 4/5 events and motion vectors.
--
Learn how Oracle Real Application Cl
I'm running todays (02. Jan) GIT and there appears to be a problem with
the mappings for the wheel on the Intuos4 pad.
First I'd like to ask what's the point of the Button4 and Button5 since
they appear to be obsoluted by RelWDn/up and AbsWDn/Up and do not have
any effect any longer.
Right now ne
89 matches
Mail list logo
