-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pointer area is not a rectangle #322
Comments
Can you share what tablet you are using? Getting the VID/PID in particular would be most helpful -- please share the output from Some display tablets are manufactured with the sensor slightly larger than the display. We normally account for this in the kernel driver so that when the pen reports proper min/max values at the screen corners. Its possible that we are not applying this correction for your particular device (and more likely with older devices where we have less info on whether the offset is needed or not). |
tablet has no display, just a black surface with a number of white dots arranged in an oddly-sized non-square grid
|
In that case, can you share more about your test setup? I don't understand what you mean by the corners having an offset, unless you mean that the sensor is offset from the white dots --- which is a manufacturing issue, not a driver issue. |
setup is... hardware mentioned above (tablet is WACOM TCL-472), for now I have configured the transformation matrix with https://github.com/petaflot/input_scaling to a centered physical 1:1 portion of the display the suggestion at #323 to use I just realized I should be able to fix this with https://en.wikipedia.org/wiki/Transformation_matrix#/media/File:Perspective_transformation_matrix_2D.svg (case 2) unless I missed something. maybe don't close the issue right now, this way I can write a procedure to calibrate such devices. |
ok.. so I was planning on going for the more general case (case 4) but even this is not the most general case because some input coordinates have a value of does the driver report negative (off-screen) values? this would really help. |
The tablet doesn't report negative values. Do you get the correct maximum (x,y) on the edges of the tablet? If those values are correct, the issue would be in the system's display mapping process. |
in absolute mode, it is clear that the corners of the pointer Area are not those of a rectangle : there is a small but noticeable offset that makes to tool useless for production purposes, and therefore just a fancy toy.
I could not find an option to calibrate the "corners" of the tablet/sensor, does it even exist?
The text was updated successfully, but these errors were encountered: