Why scrolling in KDE is so clumsy?









It's time to fix it!

Hey voidfragment,

Could you elaborate on the problem you are experiencing? And more importantly, what it is that you expect.

Because the description given seems to lean mostly towards how something isn't working, without supplying the part of how you think it should be working.
Still, I can't really figure out the 'isn't working'-part of your post as I'm playing around with the scroll bar in Dolphin myself.

BoonHead.nl, I try to say that scrolling must be predictable by using aligment for a list on the viewport. Top border of viewport should never cut icons or text (filename, size, etc)

This is still a "should not" description without an accompanying description of how you think it "should" work. But since your "should not" is now clear to me, I can speculate on what the "should" could look like.

An alternative solution to the current behavior could be: Scroll view per row. Effectively scrolling in steps the size of a row and not per pixel. I don't think it would be desirable for the view port to never cut the top of the icons because I think there is one exception: When scrolling to the bottom of the list (as shown in the screen shots of the initial post), I think it would be desirable to actually be able to reach the end of that list. This would mean that when scrolled to the bottom, the top icons would still potentially be beheaded

Is this the functionality you are looking for?

If there is a large interest, maybe this could be a configurable thing. Some users like smooth scrolling, some like a more jerky/jumpy kind of scrolling.

I do imagine jerky/jumpy scrolling (scrolling in steps) would cost less processing power, so it might be a nice option to have for energy conservative devices.
Although I would not prefer this kind of scrolling on touch devices like my mobile phone.

May I recommend you move/repost this to the Visual Design Group as you'll likely get more traction+feedback over there.

(I don't think either option will save any cpu cycles: in the one case it's just adding simple numbers to determine how far to scroll (based on mouse wheel and view settings) and moving the view port, in the other it's adding simple numbers to determine where to scroll to (based on view and mouse wheel settings) and moving the view port)

BoonHead.nl wrote:Scroll view per row. Effectively scrolling in steps the size of a row and not per pixel.

Yes! That's what I mean.

airdrik wrote:May I recommend you move/repost this to the Visual Design Group as you'll likely get more traction+feedback over there.

How to do it?

voidfragment wrote:

airdrik wrote:May I recommend you move/repost this to the Visual Design Group as you'll likely get more traction+feedback over there.

How to do it?

Just create a new thread over there with the (updated) description of your proposal with a link back to this thread for reference.