Details
-
Bug
-
Resolution: Out of scope
-
P2: Important
-
4.5.3, 4.6.0
-
None
Description
One of the change introduced into 4.4 added fallback for the un-calibrated tslib device, in src/gui/embedded/qmousetslib_qws.cpp, in void QWSTslibMouseHandlerPrivate::readMouseData()
if (calibrated)
{ // tslib should do all the translation and filtering, so we send a // "raw" mouse event handler->QWSMouseHandler::mouseChanged(p, pressed); }else
{ handler->sendFiltered(p, pressed); }this causes a problem which can be seen on customer's hardware using the examples/qws/mousecalibration example.
The mousecalibration example calls clearCalibration before calibrating, but after that the tslib driver handler goes to the "else" branch, so that the mouse data got from tslib is filtered by the sendFiltered function. some of the mouse data are lost after the filtering, which causes the calibration tool not to work properly. (the calibration tool needs raw data instead of the filtered one. maybe we need to add more API to avoid this conflict.)