Hey, I never noticed this dialog !
It lists the /WACOM Tablet Pressure Stylus/ as well as the /WACOM Tablet
Pressure Eraser/ and /WACOM Tablet Puck Tansducer/.
Initially I did not had the puck listed (I never use that).
I dropped it on the tablet for the first time whith the dialog opened and
suddendly the left mouse button event did not work anymore on the canvas,
and all of this ended with a crash.
On a fresh restart:
Regular mouse is the selection tool
Switch to the puck-> tools switches to caligraphy. Tool works but result is
shifted (cursor coordinates are different from drawn ones)
Mouse buttons do not work wile the puck sits on the tablet (but cursor
Remove the puck, use stylus: tools stay the same: works fine (no more shift)
Another funny sequence:
Use the puck ( => tool caligraphy)
switch to stylus, select tool pen, draw
back to the puck, tool stays the pen
But if in this sequence at any moment I draw with the regular mouse (even if
the tool switching occured with the stylus), when coming back to the puck,
the tool switches back to caligraphy.
If you want me to try other scenarios, jsut ask for ;)
2008/2/26, Jon A. Cruz <jon@...>:
> On Feb 26, 2008, at 9:25 AM, Jon A. Cruz wrote:
> > On Feb 26, 2008, at 5:31 AM, Aubanel MONNIER wrote:
> >> Does not work for me, checked the checkbox, restarted inkscape.
> >> Platform is WIN32, tablet is WACOM ET-0405-U, works in the gimp
> > Thanks. That's the kind of checking we need.
> > As long as you have pressure working in Inkscape, it should be
> > getting *some* extended info.
> > Can you bring up the "Input Devices..." and see what different
> > devices are listed in there? I would hope to see at least two in the
> > combo-box dropdown at the top. Getting that list from you might help.
> BTW, I just remembered one possibility. In my X11 config I have the
> ExpressKeys set up as a separate device names "pad". (That's common
> for intuos3 and graphire4 tablets I think). Anyway, to avoid getting
> the wrong things happening the code is set to ignore switches to any
> device named "pad". If that name happens to be reported for your
> configuration, you can go into desktop-events.cpp and change "pad" to
> "padXXX" or some such.
> In the near term I am working on a replacement input config dialog.
> Once that is done there won't be a need for that hardcoded work-around.