wacom tablet
System Software
Score 81%
Description:

KDE 4 KCModule

This module implements a GUI for the Wacom Linux Drivers and extends it
with profile support to handle different button / pen layouts per profile.

For hardware support have a look at http://www.linuxwacom.sourceforge.net

Project Repository:
https://projects.kde.org/projects/extragear/base/wacomtablet

get the source with
git clone git://anongit.kde.org/wacomtablet

(K)Ubuntu 12.x & 13.04:
https://launchpad.net/~maret/+archive/wacom

OpenSUSE 12.2, 12.3 & Factory:
http://software.opensuse.org/download.html?project=home:Temar:wacom&package=kcm_tablet
Last changelog:

7 years ago

+++++++++++++++++++++++++++
# v3.0.0~beta1
First kde frameworks 5 release
* port kded to kf5
* port plasma widget to qml widget
* ported KCM to kf5
* support xcb and x11_input

Thanks a lot to Michael Abrahams, Juan Palacios, Weng Xuetian, Stephan Frank

There are still some known issue with the tablet screen mapping and hotplugging with xcb.

+++++++++++++++++++++++++++
# v2.1.0
* Add support for Cintiq 22HD 18 buttons
* Add image for the Cintiq 13HD layout
* Update Wacom Intuos PT S Finger touch device db entry
* Update Intuous button layout
* Update Wacom INTUOS Pen Small CTH-480 db entry (030E)
* Add Wacom Intuos Pro L PTH-851 to db (0316)
* Allow to setup Stylus/Eraser Tip Mosue button (Left-Handed Mode)
* Update database. Add HUION, add Waltop again, install missing vendors

Note:
you must install a wacom-driver 0.20 or higher
See:
http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/xf86-input-wacom;a=summary

atrox

3 years ago

BTW, it's DELL XT3.

Report

mmdm

3 years ago

Setting express keys to the Home button doesn't work. Is there a solution? (Intuos 5)

Report

badazimer

4 years ago

if You have problem with rotation in KDE & settings is not saves(default profile is not exist):
have not nice but working decision(see screenshot - https://lh5.googleusercontent.com/-DUMD8esIEP0/Uk4E6xkrlsI/AAAAAAAABv8/Bz4k3ZlldE0/w476-h309-no/%D1%81%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA2.png):
- install plasma wacom widget
- press 2 for portrait mode
- press 1 to default landscape mode
- it works! But not very usefull: must press 2 in this position - https://lh4.googleusercontent.com/-4x_7A8rWRwI/Uk4FQt_6cVI/AAAAAAAABwc/fQ-wwc5grMU/w702-h395-no/20131004_001.jpg )

Report

rthur

4 years ago

First off, thanks for all the work - this is a life saver!

I see that in the release notes of version 2 it says there is multimonitor support yet there seems to be a slight bug for me (Lenovo x230t).
With no external monitors the rotation works as specififed.

With an external monitor however, the mapping of the pen and touch to the screen is not updated correctly - I have to go to the settings and click apply for the mapping to be updated to the monitor rotation. (I don't change any settings, seems it just doesn't update on it's own)

When connecting an external monitor the screen mappings aren't respected either - by default it streches the tablet area to span all monitors instead of just the monitor that has pen and touch support.

Are these simple bugs, or have I not set it up right?

Thanks a lot!

Report

Temar

4 years ago

Quote:With an external monitor however, the mapping of the pen and touch to the screen is not updated correctly - I have to go to the settings and click apply for the mapping to be updated to the monitor rotation. (I don't change any settings, seems it just doesn't update on it's own)

Hmm, probably we do not get the rotation event from Xorg which would explain why it works when you change some settings. I have to look into this but I'm not sure if we can easily fix it as we do not have the hardware to test it properly. I will see if I can emulate your setup using xrandr.

Quote:When connecting an external monitor the screen mappings aren't respected either - by default it streches the tablet area to span all monitors instead of just the monitor that has pen and touch support.

Unfortunately we do not have a way to detect the monitor a tablet belongs to. At least I'm not aware of one. I will look into this as well.

Quote:
Are these simple bugs, or have I not set it up right?


Sounds like bugs. As I said, we can't test these configurations as we do not have the hardware. But it's good you reported these problems so we are aware of them and can try to fix em.

Report

rthur

4 years ago

Thanks for the reply!

I'd be more than willing to help out in any way I can, I'm not familiar with your code at all, but I can test out packages / look into specific sections of it.

I completely understand that you have no way of detecting what monitor a tablet belongs too, could there perhaps be an option to permanently chose a screen to map the tablet to?

Report

Temar

4 years ago

While you already can map the tablet to a screen, it currently is not permanent if you happen to connect/disconnect the second monitor. However you can use the global shortcuts to quickly switch to a screen once you connected a second monitor.

Permanent screen mapping to a specific screen (by name) will be available once we support the new KScreen library. At the moment it'd take quite a lot of effort to reliably detect a specific monitor and map the tablet to it. This time is better spent on implementing KScreen support which would also solve some other problems we have with detecting the correct rotation of a screen.

I'm not sure when we will be able to implement KScreen support as we have quite a lot of things on our TODO list, like multi-tablet support and libwacom support. After that is done we will also be looking into KScreen support. Maybe we can implement a workaround for your problem but I first have to look into it. Proper monitor to tablet mapping however will take a while as there is lots of stuff to do to get this right.

What we could do in one of the next versions is a permanent mapping to a screen number, so it would work most of the time. However if the screen numbering changes, the configuration would be invalid again. So this would not be a final solution for your problem, just a temporary workaround until KScreen support is available.

Report

rthur

4 years ago

Using the global shortcuts does indeed fix that particular issue, and I guess it's not too much of a hassle.
Being able to assign a screen number would work for me - I doubt the monitor numbers would change that often.

This really is a small issue, the deal breaker for me has been the issues with rotation - I've reverted to using gnome and a shell script in the mean time.

While I'm unfamiliar with this project, I'm a cs major and would be more than willing to help out in any way I can.

Report

Temar

4 years ago

You are very welcome to help us! There is always lots of stuff to do and if you want to have a look at this particular issue I could help you getting into the code. We could work out a plan on how this should be fixed and of course I would be willing to assist you.

Unfortunately this issue is not trivial to fix correctly because it basically depends on knowing which monitor the tablet belongs to. It should be quite easy to make Xorg pass any rotation event (we seem to miss some) but once you know a monitor was rotated, you have to decide if you have to rotate the tablet as well.

However as a first step we could assume that whenever a monitor is rotated, the tablet has to be rotated as well. This would probably fix the issue for your setup. Still, even this simple solution has some exceptions. For instance the tablet could currently be mapped to the second monitor which did not get rotated. This raises the question if we should rotate the tablet or if the user just rotated the tablet-screen to be able to draw more easily and doesn't actually want the tablet controls to be rotated.

You see there are many things to consider so as a first step we should work out a simple feature description which lists all use cases and what should happen in which configuration. Once we know that the implementation itself should not be a big problem.

If you are interested you can contact me by e-mail.

Report

ratte

4 years ago

great thanks!

for suse 12.3 very well

Report

dentar

4 years ago

hi,
how do i set the button for the tip of the stylus or eraser when kde is using a left-handed mouse with left handed button order?
My current workaround is to issue another 'xsetwacom ... Button 1 3' for the stylus tip, a better approach would be to have a separate definition which button the tip/eraser is issuing inside the 'wacom table settings'.
Or, did i miss something?

Report

Temar

4 years ago

Quote:how do i set the button for the tip of the stylus or eraser when kde is using a left-handed mouse with left handed button order?

Unfortunately you can't. You can try to add the mapping manually to your profiles configuration file ".kde/share/config/tabletprofilesrc". However, out of my head, I'm not sure if we will remove or ignore the entry when loading the profile. You have to give it a try.


Quote:
My current workaround is to issue another 'xsetwacom ... Button 1 3' for the stylus tip, a better approach would be to have a separate definition which button the tip/eraser is issuing inside the 'wacom table settings'.
Or, did i miss something?

I wasn't aware that the left handed mode actually changes the X11 button order. We don't allow changing the stylus or eraser tip button mapping as this made problems in the past. Some tablets or driver versions did not react well when trying to change these buttons. However I'm not sure if this is still valid today.

Report

dentar

4 years ago

ok, but what about detecting the mouse button assignment and reacting accordingly inside the tablet driver tool? I know of some guys having the mouse on the left side of keyboard but still using the 'right handed' button assignment.
This would free you of implementing a tip/eraser reassignment option and still making most of the users happy out of the box?

Report

Temar

4 years ago

I think we will go for the reassignment option because it is much more flexible than auto-detecting the button order.

We just have to think of a way to disable it in case it causes trouble for some users.

Report

cryptk

4 years ago

Hello,

My pet project lately has been getting Gentoo and KDE up and running on a Samsung Series 7 Slate. Your wacomtablet kcm is great, but it was missing the data for the screen on this thing. Here is the required config for it:

[00EC]
model=unknown
layout=unknown
name=Wacom ISDv4 EC
padbuttons=0
wheel=no
touchring=no
touchstripl=no
touchstripr=no
hwbutton1=2
hwbutton2=1

Enjoy!

Report

Temar

4 years ago

Thank you!

I added it to our tablet database.

Report

msx

4 years ago

Hello Etric, I'm having all these errors, can you help me debug them?
http://pastebin.com/LYBvZTve

Cheers!
/Martín

Report

Temar

4 years ago

Your DTD does not contain the tags which are required to build the handbook. No idea why, but you can work around this problem by not building the handbook.

Edit CMakeLists.txt in the root directory and remove the line "add_subdirectory( doc )".

Report

BrendanScott

4 years ago

I have written a plugin for gimp to do mode setting for wacom intuos 5 touchring. That is, click the middle button and it cycles through the modes, making the touchring do different things zoom, brush size, layers, scroll.
The plug in is available here:
http://registry.gimp.org/node/28096

I only have an Intuos 5 touch medium, but the plug in should work with
other models. The source code has some details about setting up udev rules
so that permissions work correctly (for the status leds).

Report

BrendanScott

4 years ago

If I try to assign + (ie "key +shift = -shift) in the settings page, it records "+" but sends "=".
There seem to be problems with !@# etc as well.

Report

Temar

4 years ago

Quote:If I try to assign + (ie "key +shift = -shift) in the settings page, it records "+" but sends "=".


If you want to send a '+' sign, then the correct sequence would be "key plus". To set this, just use the button mapping dialog and press the "keyboard shortcut input button", then press Shit= and the shortcut button should correctly display the '+' sign.

Quote:
There seem to be problems with !@# etc as well.


If you tried a sequence like "key +shift 1 -shift", then it will not work as it basically translates to: "Send shift-down event, send 1, send shift-up event". As xsetwacom does not know anything about your keyboard layout, it can not translate Shift1 to '!'.

Just use the button mapping dialog and map the sequence with the keyboard shortcut button. Let me know if it works for you.

Report

BrendanScott

4 years ago

No, I configure it through kcm_tablet, and I enter a +:
click keyboard icon for ring up on express buttons tab
click spanner/Input... button
type the key + (ie shift+=).
click ok button,
click apply button

The label in the select button dialog shows a + (as does the label in the expressbuttons tab after I click ok).

BUT, when I actually "click" the ringup button I get a =:
======================================
Similarly for # and ! (the only other two I've tried)

Since then, I have tried some xsetwacom combinations, but can't get them to work either.

Report

BrendanScott

4 years ago

ps if I click a button with shift assigned to it and the ring button I get a +
If I try to assign # I get nothing on the ring click

Report

Temar

4 years ago

Quote:
ps if I click a button with shift assigned to it and the ring button I get a +
If I try to assign # I get nothing on the ring click


I tested it again and there are indeed multiple problems with xsetwacom. The '+' and '-' keys worked for me because I do not use an english keyboard layout and do not have to press the shift key to get a plus or minus.

I tried it with '!' which is also Shift-1 on my keyboard and indeed it does not work as xsetwacom does not properly map these keys. However there is help on the way and it seems future versions of xsetwacom will have a fix for this:

http://sourceforge.net/mailarchive/forum.php?thread_name=CAF8JNhKSCfjJNAgb-zjMyTEpui_RxVOV3xW3MydSUZ74o9SLgA%40mail.gmail.com&forum_name=linuxwacom-devel

We could also fix this easily on our side, like we already do for the plus and minus keys, but it seems there is another bug (or feature) in xsetwacom which somehow maps the key back to its "unshifted" base form. So in your case where you have to press Shift-= to get a plus key, xsetwacom maps this to its base form which is '='.

From my point of view this is a bug in xsetwacom, however we have to talk to the xsetwacom guys to ask how this is supposed to work. They might see it as a feature, because using "key +shift exclam -shift" actually gives you the '!'. However using "key exclam" will be translated to a '1'.

Unfortunately we can not easily work around this problem in our software. When entering a keyboard shortcut like "Shift-1", Qt returns the actual key which is "!". To translate this back into "Shift-1" we would have to take keyboard layouts into account or write our own keyboard shortcut input widget.

I think we have to talk to the xsetwacom guys first and see if they want to fix this on their side. Also I have to check the latest xsetwacom version as this bug might already be fixed.

Report

BrendanScott

4 years ago

Thanks for the feedback. I will just assign + to some other shortcut for the time being.
Apparently its already been fixed upstream:
http://article.gmane.org/gmane.linux.drivers.wacom/6721

Report

7 years ago

+++++++++++++++++++++++++++
# v3.0.0~beta1
First kde frameworks 5 release
* port kded to kf5
* port plasma widget to qml widget
* ported KCM to kf5
* support xcb and x11_input

Thanks a lot to Michael Abrahams, Juan Palacios, Weng Xuetian, Stephan Frank

There are still some known issue with the tablet screen mapping and hotplugging with xcb.

+++++++++++++++++++++++++++
# v2.1.0
* Add support for Cintiq 22HD 18 buttons
* Add image for the Cintiq 13HD layout
* Update Wacom Intuos PT S Finger touch device db entry
* Update Intuous button layout
* Update Wacom INTUOS Pen Small CTH-480 db entry (030E)
* Add Wacom Intuos Pro L PTH-851 to db (0316)
* Allow to setup Stylus/Eraser Tip Mosue button (Left-Handed Mode)
* Update database. Add HUION, add Waltop again, install missing vendors

Note:
you must install a wacom-driver 0.20 or higher
See:
http://linuxwacom.git.sourceforge.net/git/gitweb.cgi?p=linuxwacom/xf86-input-wacom;a=summary

product-maker uoowoolq Sep 08 2014

product-maker bogdancovaciu Sep 08 2014

product-maker ratte May 24 2013

product-maker msx May 01 2013

product-maker kalmar Mar 21 2013

product-maker tobaj Mar 18 2013

product-maker JenyaYQ Mar 04 2013

product-maker J0nas Feb 07 2013

product-maker HabIB Aug 12 2012

product-maker trebor Dec 26 2011

product-maker tamra Nov 03 2011

product-maker mmj Oct 24 2011

product-maker swiftscythe Sep 02 2011

product-maker saqer Jun 25 2011

product-maker wilywyrm Jun 14 2011

product-maker alltiptop Jun 03 2011

product-maker prostosuper Apr 06 2011

product-maker DannielSoares Feb 28 2011

product-maker oldium Jan 21 2011

product-maker sefran Jan 21 2011

product-maker MichauSm Jan 20 2011

product-maker bugmenot1234 Jan 15 2011

product-maker skye28 Jan 15 2011

product-maker nowardev Oct 09 2010

product-maker mosra Oct 08 2010

product-maker azagoth Oct 08 2010

product-maker chatmoa Oct 08 2010

product-maker SeaJey Oct 08 2010

product-maker titoucha Oct 08 2010

product-maker gokcen Oct 02 2010

product-maker 8 23

File (click to download) Version Description Filetype Packagetype License Downloads Date Filesize OCS-Install DL
Details
version
3.0.0~beta1
updated Oct 28 2015
added Nov 04 2009
downloads today
5
page views today 55