I've got the custom .fdi file method of configuration working great. It seems that all tool types can now be configured in this way (stylus, eraser, etc).
Here's mine as an example (adjust to taste):
/etc/hal/fdi/policy/custom_wacom.fdi
Code:
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- SGML -*- -->
<deviceinfo version="0.2">
<device>
<match key="input.x11_driver" contains="wacom">
<match key="input.x11_options.Type" contains="stylus">
<merge key="input.x11_options.TPCButton" type="string">on</merge>
<merge key="input.x11_options.KeepShape" type="string">on</merge>
<merge key="input.x11_options.Threshold" type="string">1</merge>
<merge key="input.x11_options.PressCurve" type="string">50,0,100,50</merge>
</match>
</match>
<match key="input.x11_driver" contains="wacom">
<match key="input.x11_options.Type" contains="eraser">
<merge key="input.x11_options.TPCButton" type="string">on</merge>
<merge key="input.x11_options.KeepShape" type="string">on</merge>
<merge key="input.x11_options.Threshold" type="string">1</merge>
<merge key="input.x11_options.PressCurve" type="string">50,0,100,50</merge>
</match>
</match>
</device>
</deviceinfo>
The option lines are the <merge> ones, and these may be modifed, added or removed.
I assume for the cursor and pad you can also set options if necessary.
wacomcpl doesn't work at all for me currently, but as mentioned above xsetwacom works if you use the name of the device as reported by "xinput list --short", for example:
Code:
xsetwacom set "Wacom Pen Tablet" RawSample "2"
xsetwacom set "Wacom Pen Tablet" ClickForce "1"
xsetwacom set "Wacom Pen Tablet" PressCurve "50 0 100 50"
xsetwacom set "Wacom Pen Tablet eraser" RawSample "2"
xsetwacom set "Wacom Pen Tablet eraser" ClickForce "1"
xsetwacom set "Wacom Pen Tablet eraser" PressCurve "50 0 100 50"
xsetwacom set "Wacom Pen Tablet" TPCButton "on"
NOTE: the xsetwacom commands and the <merge> options sometimes have different names... watch out
Bookmarks