https://bugs.kde.org/show_bug.cgi?id=194922
--- Comment #8 from Dave Andrews <jetdog...@hotmail.com> --- @Pascal (In reply to Pascal d'Hermilly from comment #7) > @Draciron why do you hold down the CTRL key when you scroll? > You will get the same behaviour in almost all other programs, such as a > browser, dolphin, libreoffice. > When you are holding down the Control key you can expect to get a different > behaviour. The issue is that mouse interactions are often unreliable on touch-input devices -- especially in more complicated KDE apps that are based on Kate. Right now I just pulled the latest version of KDevelop, which makes heavy use of the Ctrl+ modifier during mouse operations (particularly when ctrl+clicking on variables to follow them!) On touch-input devices, when trying to do precision touch events -- scrolling is often applied incorrectly when: -Performing precision single-finger gestures. -Moving into the edge regions of touchpads. -Dirty, Abused, or Disfunctional touchpads. -Owning a larger touch pad (i.e. gaming laptops / touch devices) The problem is compounded with synthetic touchpad driver events (someone trying to workaround this here -> https://git.reviewboard.kde.org/r/120319/), which give the gesture acceleration + deceleration long after the user tries to stop the incorrect input. This leads to having your Kate/KDevelop document look like anything from the size of a breadcrumb -- to the size of Texas! =) You're right that this deserves a central way of controlling this for editor zooming, but in the absence of that, I'm going to have to patch this out of my machine's kate binaries while using an otherwise perfect editor -- because it's incredibly hard to use on touch devices without this! -- You are receiving this mail because: You are watching all bug changes.
