Version: 2.0.85 (using KDE 4.6.2) OS: Linux Hi, I've just activated Dynamic Word Wrap. I don't know if this is really a bug, but when I scroll with my mouse wheel, rows which are splitted by Dynamic Word Wrap are treaten as one row, which means that the whole block is jumped with one turn of my wheel. Reproducible: Always OS: Linux (x86_64) release 2.6.38-8-generic Compiler: cc
Forwarding to KatePart.
Yeah, thats by design. We work "real line" based for any text positioning.
this is highly undesirable behavior. with long paragraphs the scroll wheel is essentially useless
Right, but it's unfixable, as otherwise we have to layout the entire document just to know how many lines are really there given dynamic word wrap. We have had several reports about it, but the decision won't change nevertheless. Sorry.
> it's unfixable, as otherwise we have to layout the entire document Could you please be more specific or point me to a discussion why that is the case? Given, that the shortcuts "Scroll Line Down" and "Scroll Line Up" already do the right thing (defaults: <Ctrl>+<Down> and <Ctrl>+<Up>), i.e. scroll one line in the view and not from one new line character to the next, a fix sounds trivial. Because instead of whatever code is used at the moment, the mouse wheel event should call exactly the aforementioned "Scroll Line" code n times, where "n" is defined in systemsettings -> Input Devices -> Mouse -> Advanced -> Mouse wheel scrolls by "n" lines.
I've searched for information on this bug after finding it quite annoying in my installation of Kile. The only information I found was this bug report. So, I also would be very interested in information on where this has been discussed before and why it would be so difficult to fix. This is a major annoyance and deserving of attention. The fix also seems trivial: the wheel should single scroll x lines the same as the aforementioned Scroll Line Down and Scroll Line Up shortcuts.
It's fixed to some degree in KDE 4.8, please read comment #7 and comment #10 in bug #231616. *** This bug has been marked as a duplicate of bug 231616 ***