SUMMARY When I move an album in albumtreview, I will get a popup which asks me "move here/cancel". I would like to disable this popup because there is no need for this. While digikam is rescanning folders this popup will lead me to messed up albums. STEPS TO REPRODUCE 1. drag one album in album treeview 2. sometimes this is quiet! laggy (while rescanning) 2. move somewhere else (release button) 3. popup will show up 4. you have to click again OBSERVED RESULT sometimes this popup is quite laggy (while file operations occur). this will lead me to drop albums into a wrong place. EXPECTED RESULT Some way to cancel this popup (or just delete it?). SOFTWARE/OS VERSIONS Windows: MacOS: 10.14.2 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Thanks for this great software! :-)
Just wanted to file a similar wish. I would love this too. This popup keeps me from using this great software. Please delete it. Or add some key "SHIFT+drag/drop" or "ALT+drag/drop" for moving/copyign. And ESC to cancel drag&drop.
I have to admit that I really like the popup menu. I also know the bug report at Dolphin on the subject. I'm relatively quick with the mouse, under Windows it happens that a folder is moved via Dra&Drop, which you didn't want. Similar to Dolphin currently, I would add Ctrl / Shift to move or copy directly. Maik
Maik, Take a care, this report is about MacOS version where "Ctrl" modifier has another behaviour than under Linux or Windows. Apple use "Command" function key here... https://en.wikipedia.org/wiki/Command_key Wikipedia propose a very comparison page about modifier keys by OS : https://en.wikipedia.org/wiki/Table_of_keyboard_shortcuts Gilles
Could someone point me to the direction where to change this? I am developing mostly in python but I know C++ and Swift as well. Maybe I can take a look? But I am not used to open source contributions except tensorflow and have no idea where to start with this. What module, what git directory. Can someone give me an entry point for this?
After a quick look at the code, I see that it already exists for items. Shift key move items, Ctrl key copies an item without a popup menu. I will add the same logic for albums. Maik
digiKam 7.0.0 stable release is now published and now available as FlatPak: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier
Still no luck. Tested digicam 7.0.0 and shift / control keys do not work with albums on OSX Catalina (10.15.6 (19G73)) (In reply to caulier.gilles from comment #6) > digiKam 7.0.0 stable release is now published and now available as FlatPak: > > https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ > > We need a fresh feedback on this file using this version. > > Thanks in advance > > Gilles Caulier
https://bugs.kde.org/show_bug.cgi?id=426938 --- Comment #4 from caulier.gilles@gmail.com --- Hi, digiKam 7.2.0-beta2 pre-release PKG installer now support BigSur and is compiled with last stable Qt 5.15.2. https://files.kde.org/digikam/ Problem still reproducible with this version. Thanks and happy Christmas in advance Best Regards Gilles Caulier
I also do still get the popup. also using shift key. also i get 3 options explained but only 2 available (the one i want is missing :( ) Files or folders with the same name already exist in the target folder. What action is applied in the event of a file conflict? Available options are: Rename automatically: conflicting files will be renamed. Overwrite automatically: conflicting files will be overwritten. Skip automatically: conflicting files will be skipped. buttons i get to chose from are rename and skip and cancel. please add overwrite button
The button for overwriting is of course available here. Which digiKam version are you using? Which operating system are you using? I already suspect that the button is suppressed from some GUI guidelines, since it technically corresponds to the "no" button. Maik
*** Bug 261564 has been marked as a duplicate of this bug. ***