Created attachment 104198 [details] EditTag In Edit Tag -> Shortcut, when Input... appears and I press any key combination, a conflict warning dialog always appears regardless of whether the key combination currently exists or not. In addition, for an existing assigned key combination, it is not displayed in the dialog. See the attached picture.
Hi Hardy, The problem still reproducible using current 6.1.0 pre-release installer for Windows available here : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
Hi Gilles, Thank you but the problem is still present.
This may be a stupid question but when it says Meta+Ctrl+F2 what is the Meta key?
Meta is the key with the "Windows" logo on latin1 keyboards. https://www.computerhope.com/jargon/m/meta-key.htm Gilles Caulier
digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier
The problem is still there but slightly different behaviour from what I recall. If the shortcut already exists, it correctly warns about the conflict with details about the conflict. If the shortcut does not exist, the stock warning appears as previously reported.
I can confirm that this issue is still there in 7.2beta2 64bit on Windows 10. Note that if you ignore and override the "conflict" everything works, but it looks very scary. I initially spent long time trying if at least something is not causing any conflicts.
I am currently working with version 7.2 and the bug still exists here. In this context I also noticed that tags cannot be assigned with single keys, but only with key combinations like Ctrl+..., Alt+ ..., Ctrl + Shift + ..., etc. Possibly a bug of its own?
Please check with next 7.3.0 release : https://download.kde.org/stable/digikam/7.3.0/
Created attachment 140006 [details] S1 - Conflict Dialog
Created attachment 140007 [details] S2 - Config Screen scrambled
Created attachment 140008 [details] S3 - But assignement successful
Created attachment 140009 [details] S4 - Same behaviour on Tag Key Assignment
I am sorry. But even with 7.3 nothing has changed in the behavior. See the screenshots S1 to S4. As in 7.2 the message appears, but when clicking on "Reassign" the assignment remains and the shortcut is set. The same behavior with the tags. However, only shortcuts with control keys can still be used here.
This keyboard shortcut editor comes from the KF5 framework. I don't see any Windows specific code there. I think the editor simply has no overview of the global keyboard shortcuts defined in Windows. There will be no solution here in the short term. It would be to test whether it works in Krita. Maik
Krita 4.4.5 on Windows 10 64bit works correctly. Conflicts with shortcuts are detected correctly and reported only when they occur. I have also tested the negative cases. Krita works absolutely flawlessly. I hope that the information helps. Michael
This feature is EXACTLY what I need from digiKam so it is disappointing that this bug has persisted for over four years. I can confirm what Micheal reports, it works in Krita.
I have the same, or at least a similar, problem using digiKam 7.6. It was also present in 7.4 and 7.5 but I didn't report it then, assuming that it would be fixed in the next version. I had assigned the F1 key to 'Pick label "Rejected"' which was reported to be in conflict with 'digiKam Handbook'. When removing the assignment, digiKam starts up without displaying the error messages. However, the F1 key does not seem to do anything. Under 'Help', I see that the 'Online Handbook' (is that the same as the 'digiKam Handbook'?) is assigned to F10 and this key (F10) does indeed bring up 'Revision 7.0' of the handbook. But the disputed F1 key does nothing (that I can see) and I haven't been able to determine that it is actually assigned to the handbook, i.e. I haven't found the place where that assignment is done. I have a screendump named digiKam_bug_376859.png which I'll try to attach.
Created attachment 148497 [details] The bug is still present in digiKam 7.6 I had assigned the F1 key to 'Pick label "Rejected"' which was reported to be in conflict with 'digiKam Handbook'. When removing the assignment, digiKam starts up without displaying the error messages. However, the F1 key does not seem to do anything as far as I can see. Under 'Help', I see that the 'Online Handbook' (is that the same as the 'digiKam Handbook'?) is assigned to F10 and this key (F10) does indeed bring up 'Revision 7.0' of the handbook. But the disputed F1 key does nothing...
(In reply to Staffan from comment #18) > I have the same, or at least a similar, problem using digiKam 7.6. It was > also present in 7.4 and 7.5 but I didn't report it then, assuming that it > would be fixed in the next version. > > I had assigned the F1 key to 'Pick label "Rejected"' which was reported to > be in conflict with 'digiKam Handbook'. When removing the assignment, > digiKam starts up without displaying the error messages. However, the F1 key > does not seem to do anything. Under 'Help', I see that the 'Online Handbook' > (is that the same as the 'digiKam Handbook'?) is assigned to F10 and this > key (F10) does indeed bring up 'Revision 7.0' of the handbook. But the > disputed F1 key does nothing (that I can see) and I haven't been able to > determine that it is actually assigned to the handbook, i.e. I haven't found > the place where that assignment is done. > > I have a screendump named digiKam_bug_376859.png which I'll try to attach. I might add that I'm using the digiKam-7.6.0-x86-64.appimage on Linux; currently Linux Mint 20.3 (previous versions 7.5 and 7.4 on Linux Mint 20.2).
Neither F1 nor F10 is assigned to the manual in the digiKam default settings. This is probably an automatic assignment in your desktop operating system. Maik
(In reply to Maik Qualmann from comment #21) > Neither F1 nor F10 is assigned to the manual in the digiKam default > settings. This is probably an automatic assignment in your desktop operating > system. > > Maik That does indeed seem to be the case. Thanks!
I cannot reproduce the problem here under Windows with F1 and F10 keyword shortcuts. As explained in the digiKam documentation none of both keys are assigned in digiKam. This must be a problem in your OS settings, as Maik explained in comment #21. I close this file now Gilles Caulier