Quote:
Originally Posted by jayk
Real quick - I have managed to replicate the problem. It does appear to be inside the x server, as other tslib based programes (namely the ts_print / etc) all get immediate response from the tablet. I've not had a chance to dig into it too deeply yet, but I thought I'd send a note and let you know I have at least looked at it. I'll keep you posted.
|
FYI - I've tracked this problem down and corrected it in my local sources. Looks like the tablet sometimes produces some trash when you first power the iLiad up. In some cases this trash could be interpreted as the first couple of events in the tslib code (if the bytes that normally indicate sync matched up with what the code expects the sync bytes to look like)
Long story short is that we were getting coordinates that made no sense at all... and the X server was dutifully ignoring them. Once some real events came through, it would sync up and start working again.
I've solved this problem by putting the device query in to the initialization routine. Even though we don't need / care about the tablet size, etc.... it does clear out the cruft and eats the garbage data before the x server has to deal with it.
I have not packaged it up yet, but I will do so, probably tomorrow, and put it online.
JayK