[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: Krita wacom settings.
From:       Dmitry Kazakov <dimula73 () gmail ! com>
Date:       2013-04-02 6:42:10
Message-ID: CAEkBSfVbYu58YapZnbD=qG4c0a2VfMyCcVeqZqOpwoJQtwZn2g () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi, Simon!

This offset bug is really interesting :) I have such a feeling that Qt
handles the tablet and mouse events somehow differently... I wanted to ask,
do you compile Krita yourself or use some packages? Just in case you
compile it, I could prepare a patch that would show some debug info and
proof whether my idea is right...

Could you also send me the output of the following commands:

1) xrandr
2) xinput --list                                          # << here you
should find the ids of your wacom tablets
3) xinput --list-props <id_of_your_intuos>
3) xinput --list-props <id_of_your_cintiq>


PS (technical part):
I guess, that the problem is that while hovering we use the coordinates
values from QMouseEevnt, which are generated by the X11 and have the
transformations set by xinput, but while doing the stroke we use
QTabletEvents, which might use some Qt's home-grown drivers, which, in
turn, might not have support for xinput transformations. It might also be
interesting to check the configuration: 2 monitors + 1 tablet set up for
one of them.

-- 
Dmitry Kazakov

[Attachment #5 (text/html)]

<div dir="ltr"><div><div><div><div><div>Hi, Simon!<br><br></div>This offset bug is \
really interesting :) I have such a feeling that Qt handles the tablet and mouse \
events somehow differently... I wanted to ask, do you compile Krita yourself or use \
some packages? Just in case you compile it, I could prepare a patch that would show \
some debug info and proof whether my idea is right...<br> <br></div>Could you also \
send me the output of the following commands:<br><br></div>1) xrandr<br></div>2) \
xinput --list                                                                         \
# &lt;&lt; here you should find the ids of your wacom tablets<br> </div>3) xinput \
--list-props &lt;id_of_your_intuos&gt;<br>3) xinput --list-props \
&lt;id_of_your_cintiq&gt;<br><div><div><div><div><div><div><div><div><div><div \
class="gmail_extra"><br clear="all"><br></div><div class="gmail_extra"> PS (technical \
part):<br></div><div class="gmail_extra">I guess, that the problem is that while \
hovering we use the coordinates values from QMouseEevnt, which are generated by the \
X11 and have the transformations set by xinput, but while doing the stroke we use \
QTabletEvents, which might use some Qt&#39;s home-grown drivers, which, in turn, \
might not have support for xinput transformations. It might also be interesting to \
check the configuration: 2 monitors + 1 tablet set up for one of them.<br> </div><div \
class="gmail_extra"><br>-- <br>Dmitry Kazakov \
</div></div></div></div></div></div></div></div></div></div></div>



_______________________________________________
Krita mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop


[prev in list] [next in list] [prev in thread] [next in thread]