https://bugs.kde.org/show_bug.cgi?id=360478
--- Comment #60 from Nate Graham <n...@kde.org> --- (In reply to Uwe Dippel from comment #59) > We actually proposed some remedial concepts; and I wonder why 'the > developers' respectively the designers of Plasma 5 do not take any > responsibility for their oversight, and propose a coherent concept for > behaviour with changing resolutions. > Just storing and retrieving a setting for each of the possible resolutions > is nothing more than a temporary workaround, since a new resolution ought > not force the user to redefine screen layout. The same reason any bug isn't fixed or feature isn't implemented: because the developers are spending their time fixing things deemed to be of higher urgency (for example, making clipboard functionality and pasting work on Wayland). I'm starting to feel like a broken record here. It's understandable that folks are frustrated, but asking "why isn't this fixed yet?" won't make it happen faster. Instead, it will demoralize and de-motivate the developers who happen to be CCs on this bug report who don't have an extremely thick skin and make it *less* likely that they will want to work on it, not more. The more comments and arguing are in a bug report, the more demoralized the average person becomes when reading through it--this includes any developers who feel like fixing the issue. So complaining in the bug report is not generally an effective approach. If you want to see the issue get resolved faster, the options that work include: - Working on it yourself - Finding a technically competent friend or colleague to work on it for you - Writing a polite blog or social media post about it to draw attention to the issue and find someone to work on it - Paying a developer to work on it -- You are receiving this mail because: You are watching all bug changes.
