I doubt it. For instance when making a simple slider, if I don't add any functionality to a draggable rectangle it follows my input really fast. As soon as I attach a handler to the signal"onPositionChanged" (mousearea ) or for instance to the signal "onXChanged" (rectangle) it stops following my finger after certain speed and jumps to last postion when I stop. At the same time also signals stop triggering my handlers until I stop moving my finger. Based on this observation it is hard for me to believe that the problem is in the device or the driver.
2014-05-28 10:20 GMT+02:00 Rutledge Shawn <shawn.rutle...@digia.com>: > > On 27 May 2014, at 3:06 PM, Georgije Bosiger wrote: > > > From what I've seen it turns out that the problem is in > "onPositionChanged" signal. For some reason attached handler to this signal > is not executed on faster movements when evdevtouch is used, but it's OK > for the evdevmouse. This realization lead me to use the timer instead, so > that now I make changes on defined interval while touch is pressed. This > way response to the input is fast. > > It's too bad that you need a workaround, so it would be nice to narrow > down why it happens. I don't think we were trying to do event compression > until https://codereview.qt-project.org/#change,82975 , but that's only > on dev branch so far… so I guess it must be happening in the device or the > driver. > >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
