[dolphin] [Bug 468749] "Selection mode" shortcuts are not changeable / can not be disabled

2023-04-24 Thread Felix Ernst
https://bugs.kde.org/show_bug.cgi?id=468749

Felix Ernst  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #3 from Felix Ernst  ---
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 ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 468749] "Selection mode" shortcuts are not changeable / can not be disabled

2023-04-22 Thread Julius R.
https://bugs.kde.org/show_bug.cgi?id=468749

--- Comment #2 from Julius R.  ---
(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!

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 468749] "Selection mode" shortcuts are not changeable / can not be disabled

2023-04-21 Thread Felix Ernst
https://bugs.kde.org/show_bug.cgi?id=468749

Felix Ernst  changed:

   What|Removed |Added

 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from Felix Ernst  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.