https://bugs.kde.org/show_bug.cgi?id=369349
--- Comment #34 from alvinhoc...@gmail.com --- > I have a feeling that there is some bug in how we handle the events flow. We > should first try to fix it, instead of giving the user an option to control > such non-obvious property. > > As a direction of further work, it might be a good idea to have a log of how > many events are usually handled in > > KisStabilizerDelayedPaintHelper::stabilizerDelayedPaint() > > when isEndStroke is false. > > If the number of events is always the same, then my theory is probably not > correct. If it interleaves with zero like "10,0,11,0,9,0...", then my theory > is correct. I am taking a guess that the timer resolution may also affect the behaviour. IIRC it isn't using a high-resolution timer so maybe there is some fuzziness which depends on system load? -- You are receiving this mail because: You are watching all bug changes.
