https://bugs.kde.org/show_bug.cgi?id=354227
--- Comment #23 from Sebastian Kügler <se...@kde.org> --- @MN Simply raising the priority doesn't do much, and it shouldn't be done based on how long a bug is open alone. So we have been working on a redesigned KCM for KScreen, but it's a lot of work and not many hands helping. I've been chugging at it for some weeks, and I'm not nearly finished since other (kscreen) tasks take a lot of time as well, going over bugreports, answering them, fixing problems that prevent users from working and all that. Something that would definitely make a difference is someone helping with the work on the new KCM, or more people like Christoph who help with bug triaging. Making sure that kscreen works in all its aspects is very much a shared responsibility, and while I'm the maintainer of these components, I can only do so much on my own. The new KCM, when it lands (not before 5.10 for sure), is supposed to fix this and a series of other UI problems, improve wayland support and make the code more maintainable in the long run. On top of that, there's some more work on general usability aspects involved. Doing this without regressions is a time-consuming task costing lots of work, so help is very much welcome. You're saying that the solution is to simply add scrollbars (if I interpret it correctly, if not, please clarify). These scrollbars are in fact automatically added when you run the KCM in system settings, but kcmshell5 doesn't have this feature (a known bug). It's wrong to just add the scrollbars in kscreen's kcm as that would lead to double scrollbars in system settings, and instead of adding complex conditional magic, perhaps fixing kcmshell5 is the better option. -- You are receiving this mail because: You are watching all bug changes.
