https://bugs.kde.org/show_bug.cgi?id=385270
--- Comment #12 from Nate Graham <n...@kde.org> --- Making it configurable only helps the people who know that it's configurable, care to configure it, and remember that they configured it. If we made it configurable but left "change-on-scroll" enabled by default, then it wouldn't change for new users just switching, so your claim would still stand. Most people don't configure anything. If we made it configurable but disabled it by default, this would have the effect of removing the feature for 99.99% of people because, again, most people never configure anything. And it would be quite annoying for the people who like this feature, most of whom would not know that it is configurable or where to configure it. And disabling this feature for views that aren't scrollable would be totally pointless since there is no problem there. The potential problem exists only in scrollable views; for non-scrollable views, it is a nice timer-saver. So making it configurable wouldn't really help there. In the end, I think our compromise is a good one. It was actually conceptualized by a UX designer. So perhaps he's the one who knows what he's doing, and you should have more faith in our design process. :) Anyway, I just wanted to give some explanation and am not really in the mood to argue, so this will be my last response. -- You are receiving this mail because: You are watching all bug changes.
