![]() Registered Member ![]()
|
Yep run dual monitors and have a Huion H610 graphics tablet. 6 months ago.
And didn't run in Krita pre-2.8 Linux side but worked in Windows 7 side. Fast forward to present and 2.9.1 works great in both OS'es But on Linux tablet spans both monitors. And don't see a setting for limiting Krita to one monitor. Or a way to assign the Action keys to actions. As stands now active area on tablet covers both monitors. Can draw only using 1st half of area. ![]() Any help on this? As don't see any linux based tablet apps like windows. Where you can in windows setup calibration and assign my 8 keys to Krita actions. Assign stylus buttons actions and switch it to left-handed drawing. Anything in the works? 3rd party? Hacks or solutions to this situation? Thanks any help insights into this is greatly appreciated. As have to boot to Windows 7 side to use tablet to it's fullest. . |
![]() KDE Developer ![]()
|
If it were a wacom, I'd say you need to use the xsetwacom commandline utility. Looking at the faq, I think that you should be able to do this with xinput_calibrator.
|
![]() Registered Member ![]()
|
I was afraid of that as more a general hack than a solution. As found the instructions on Krita FAQ.
Guess I'll have to deal with it and try fiddling with. . |
![]() Registered Member ![]()
|
I'm having this same problem however I am using a wacom tablet and I use windows 7 x64 Professional. I'm using the Wacom Intuos Pro touch. Krita completely ignores the fact that I only have the tablet limited to one of the 2 monitors. I am not having this problem on any other program. As soon as the Krita program is selected, it starts ignoring the the bounds and makes my tablet surface span the entirety of both of my monitors. Please help!
Also, please note I am not savy with code or anything like that. I'm just an artist so I dont really know anything about command line features and stuff like that. x.x |
![]() Registered Member ![]()
|
Sorry don't have issue using my Huion with Krita in Windows 7 as the installed huion software dialog allowed me to choose which monitor and works as expected. Using version 2.9.1 as earlier versions I did have issues. So if opening up your Wacom software and have the right monitor chosen where Krita opens on selected. Don't know what else I can think of that will help.
. |
![]() Registered Member ![]()
|
This is too bad. Thanks for the reply anyways. I'm not sure what to do. I have even tried updating my Wacom drivers. It doesn't make any difference at all. I tried assigning different screens, or even using a portion of the monitor instead. Nothing effects it at all. Unfortunately since this is problem that only is effecting Krita I can't find any solutions anywhere. I am unable to determine if this is a unique problem to just me or if others are having the same issue.
|
![]() Registered Member ![]()
|
Probably this a solution for you:
or:
|
![]() Registered Member ![]()
|
Enjalu is correct, this is normal default behaviour for the xinput system -- it maps the pointer device to the entire extended desktop.
You can reset the range by hand as enjalu suggests, but it got a bit annoying for me and a colleague so we started developing a simple GUI called PTXConf. It would be helpful if people would try it out and see if it is useful, see instructions here: http://wenhsinjen.github.io/ptxconf/ All you should have to do is select your input pen or touch device and then select which monitor you want to map it too, all graphical. Maybe some Linux distros already have such a GUI tool... we don't know... but Ubuntu at least messed it up by only supporting Wacom pen devices for this... quite silly we think, because xorg xinput already supports this reconfiguration for many years. Anyway please try it, we need some input on how it works with your devices and screen setup. |
![]() Registered Member ![]()
|
Wow, why are all these methods so darn complicated?
I find this much easier:
No calculations necessary! No weird xinput_calibrator necessary! hooray! |
Registered users: Baidu [Spider], Bing [Bot], Google [Bot]