View Single Post
Old 03-02-2018, 01:15 AM   #17
mdp
Wizard
mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.mdp ought to be getting tired of karma fortunes by now.
 
Posts: 1,481
Karma: 9010563
Join Date: Jul 2013
Device: none
Quote:
Originally Posted by sogaiu View Post
Investigating along these lines further...

The Draw app has a custom view that implements onTouchEvent so I added some logging to see how fast that was. It seemed just as fast with my finger as with the stylus (in both cases, seemed speedy enough). I tried with Onyx's TouchHelper enabled as well as disabled with results that didn't seem different subjectively.

The time it takes for strokes to appear on the screen is slow as before of course -- so detection / responsiveness(?) does not appear slow. It seems there is something subsequent to receiving the events which is not fast enough. Does that make sense?
Sorry: do you mean that, in the custom application, touch and pen input trigger the events quickly, but the strokes appear with delay?
In that case, there is something wrong in the screen update.

Probably there exists a method that suspends screen update buffering?

But was not it noticed that with a mouse the experience may be surprisingly different? Have you tried to se if the inconsistency also appears in Draw?

Last edited by mdp; 03-02-2018 at 01:17 AM.
mdp is offline   Reply With Quote