STEPS TO REPRODUCE 1. I recently noticed, that hardcoded keyboard shortcuts (space, F2) were introduced in Dolphin, activating the so called "selection mode". CHANGE PROPOSAL As for as I understand, it is the design philosophy of KDE to be customizable in mosts aspects, especially regarding the workflow of the user. Actually, this is the selling point (imho) that distinguishes it from DEs like GNOME. I therefore would kindly propose the idea of: Adding the ability to change or disable the selection mode shortcut. Further, it might be a good idea to prevent hardcoded changes for keyboard shortcuts in the future, possibly by introducing respective design guidelines? SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.2.10-1 Manjaro KDE Plasma Version: 5.27.4 Qt Version: 5.15.8 ADDITIONAL INFORMATION Thanks to all developers for their hard work!
See https://bugs.kde.org/show_bug.cgi?id=466050 for details. Is it okay for you if I mark this bug report as a duplicate? >Further, it might be a good idea to prevent hardcoded changes for keyboard shortcuts in the future, possibly by introducing respective design guidelines? Don't worry, there is no interest in hardcoding shortcuts if this can be prevented. In this case it was a quick change to fix two potentially bigger bugs in a smaller update which we knew would cause this smaller bug.
(In reply to Felix Ernst from comment #1) > See https://bugs.kde.org/show_bug.cgi?id=466050 for details. Is it okay for > you if I mark this bug report as a duplicate? Of course, sorry, I've missed that one! > > >Further, it might be a good idea to prevent hardcoded changes for keyboard shortcuts in the future, possibly by introducing respective design guidelines? > > Don't worry, there is no interest in hardcoding shortcuts if this can be > prevented. In this case it was a quick change to fix two potentially bigger > bugs in a smaller update which we knew would cause this smaller bug. Then I am relieved. I had no idea about the bug avalanche in the background, makes all sense now. Thanks!
Well, "bug avalanche" is maybe a bit of an overstatement. The two bugs weren't quite that grave for the average user. ^^ *** This bug has been marked as a duplicate of bug 465489 ***