Closed GoogleCodeExporter closed 9 years ago
Are you referring to the extended input causing the cell widget to be disabled
almost
at random when using an wacom digitizer? In this case I second that patch ...
Original comment by mfl...@gmail.com
on 22 Feb 2009 at 11:09
This only disables extended input events in case they are not being reported
correctly due to incorrect configuration or a bug somewhere. They are only used
for
the eraser at the moment as CW does not use pressure data during recognition.
If the
cell widget is getting disabled that is another issue entirely. If anything, it
should work more reliably with extended input events disabled!
Original comment by risu...@gmail.com
on 9 Mar 2009 at 8:45
As I understand it, XInput is also a much higher resolution system than
traditional
input events.
Original comment by jldug...@gmail.com
on 15 Mar 2009 at 9:34
What I know about it is that when I created that patch, it solved the problem,
so I
submitted it to Launchpad.
Without the extended input enabled, Cellwriter does not work very well on my
Lenovo
Thinkpad X61 Tablet running Ubuntu.
When it is enabled, and I draw a letter and I draw over the edges of the
cellwidget,
it sees that as an invalid input and disables extended input. From then on,
Cellwriter won't respond to the stylus at all, and I have to restart it.
And yes, of course, the eraser does not work without extended input events
enabled.
As far as XInput being a much higher resolution system goes, I'm sure that's
true in
that the Wacom tablet has a higher resolution than the display. But I am
certain that
the input x and y coordinates being used by Cellwriter are scaled to screen
resolution at the point where they are being used in cellwidget.c where the
patch
applies.
It just works with the patch, and does not work without it.
There is a separate bug, very probably not on Cellwriter, where when the tablet
screen and associated wacom tablet device are rotated, the calibration is lost
or
something and it stops working right. It worked fine for a while, then something
changed and it did not, then it worked again... I'll try and figure out what's
going
on with that. It's probably a problem with the xserver-xorg-input-wacom driver
itself, if it's not already fixed.
Original comment by Karl.Heg...@gmail.com
on 8 Feb 2010 at 2:12
Remove this bit of code. Invalid coordinates are now silently ignored.
Original comment by mele...@google.com
on 8 Oct 2011 at 6:30
Original issue reported on code.google.com by
jldug...@gmail.com
on 5 Jan 2009 at 8:26Attachments: