| Summary: | Shift+delete shortcut | ||
|---|---|---|---|
| Product: | [Applications] gwenview | Reporter: | DrSlony <bugs> |
| Component: | general | Assignee: | Gwenview Bugs <gwenview-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | archenroot, bugs, elvis.angelaccio, hj.vanwilligen, jkt, joao.eiras, myriam, rdjmclean, simonandric5, xmltwig |
| Priority: | NOR | ||
| Version: | 5.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | https://commits.kde.org/gwenview/3dc1b04284e2db026f0eec15828ed99ce9aa484f | Version Fixed In: | 16.12.1 |
| Sentry Crash Report: | |||
|
Description
DrSlony
2015-05-07 09:38:07 UTC
same problem on kubuntu 15.04. Additionally shortcuts are not saved even when changed, so I can only remove this shortcut for the current session. Trying to save the configuration through configure shortcuts / details/more actions / save as scheme default does not save the new configuration either. It is due to kconfigwidgets specifying that the standard action for "Cut" has Shift+Del as a secondary shortcut. Tracking the history of that was rather funny, but it seems that it dates back to 2001, http://quickgit.kde.org/?p=kdelibs.git&a=commitdiff&h=3a7bc675a which adds this: + { I18N_NOOP("Cut"), 0, Qt::CTRL+Qt::Key_X, 0, Qt::SHIFT+Qt::Key_Delete }, ...despite the misleading commit message. Since that time, this alternate shortcut was kept unchanged. It's a question whether it's reasonable to remove it today. As a user, you can "fix" this by removing the Cut's alternate shortcut by setting it as "custom" and not entering any shortcut. We could change this in gwenview of course, similar to how it got done in Digikam in https://bugs.kde.org/show_bug.cgi?id=286212 which leads to http://quickgit.kde.org/?p=digikam.git&a=blobdiff&h=10d5384210027ad974cace90e41dbe11689b95ea&hp=0486238971d837cd0e87d4fd55f08b3b957cbf71&hb=bdf416be9a5dcc3aedc58e64718b222890c49600&f=digikam%2Fmain%2Fdigikamapp.cpp . However, if there are multiple apps essentially undoing this default, maybe it makes more sense to nuke it once and for all in kconfigwidgets. Shift+Delete for forced removal of an item is IMHO much more common than "Cut". Yes, shift+delete should not "cut" by default. It should not be required for the user to change this manually, but rather to set it manually, if the user comes from a planet where shift+delete is used to cut ;] "As a user, you can "fix" this by removing the Cut's alternate shortcut by setting it as "custom" and not entering any shortcut." Which currently does not work due to 343960 Git commit 3dc1b04284e2db026f0eec15828ed99ce9aa484f by Albert Astals Cid. Committed on 29/12/2016 at 17:20. Pushed by aacid into branch 'Applications/16.12'. Manually fix Shift+Delete shortcut ambiguity REVIEW: 129718 M +3 -6 app/fileopscontextmanageritem.cpp https://commits.kde.org/gwenview/3dc1b04284e2db026f0eec15828ed99ce9aa484f *** Bug 377880 has been marked as a duplicate of this bug. *** When double clicking in Dolphin on a .jpg file to open it, gwenview shows error ¨There are two actions (Cut, Delete) that want to use the same shortcut (Shift+Del). This is most probably a bug. Please report it in bugs.kde.org¨ So, here you are. |