Version: (using KDE 4.1.1) OS: Linux Installed from: Debian testing/unstable Packages There is only one overall setting for the mouse scrolling speed in systemsettings. Ok, it was the same in KDE3's kcontrol - but in KDE3 that setting didn't have much effect on the filemanger (even with a setting of let's say 8 lines it was a smooth scrolling of just 1,5 icons height). In KDE4 it does, a line seems to be an icon line - and that's the problem. When I use a browser comfortable scrolling speed of 3 lines or more I cannot visually keep track of the scrolling files in the filemanager because the scrolling is too jumpy. I am only able to work with the filemanager when I set the scrolling speed to 1 single line. But that is far too slow for me when I use the browser. So please separate scrolling speed setting for browser and filemanager.
I think this is more important than wish-list. This makes working with rich lists very annoying. If you scroll once with your mouse, you will actually miss some list items.. here is an example ------------ list visual boundaries ------------ item 1 item 2 item 3 ------------ /list visual boundaries ------------ do a one time scrol with the mouse wheel, you get: ------------ list visual boundaries ------------ item 7 item 8 item 9 ------------ /list visual boundaries ------------ you will completely miss out item 4, 5 and 6. This happens when you scroll "install new themem" in system settings, and no other modifications done to the system (out of the box Fedora 12) It is not only that you miss some items, but you will be completely lost in the list, there should some visual guides to help keep tracking of the list, such as, after the first wheel scrool, you still get the last item from the last view: ------------ list visual boundaries ------------ item 3 item 4 item 5 ------------ /list visual boundaries ------------
This isn't technically feasible, nor practically useful now that most of KDE's own browsers are defunct and most of us use Firefox or Chromium these days. Also, with no duplicate reports, patches, or developer interest in 14 years, I think it's safe to say it won't end up happening, sorry. :)