Description: General LibreOffice shortcuts should be visible even if you select any module on Keyboard tab in Customize dialog Steps to Reproduce: 1. Open Writer 2. Open Customize dialog using Tools menu 3. Select Keyboard tab 4. Make sure you have selected Writer radio button in top right corner 5. Click inside Keyboard area and press Ctrl+Alt+4 shortcut 6. You see the shortcut is free (it did not assign to any command) 7. But if you select LibreOffice radio button in top right corner, click in Keyboard area again, and press Ctrl+Alt+4 shortcut, then you'll see that shortcut is using! It using just in all modules for Sidebar's Navigator opening! So I suggest to show all using shortcuts in Keyboard area regardless of selected the radio buttons. It may be for example just have grey font color, as it's for some predefined system shortcuts like Ctrl+F4. So after this change user can see all used shortcuts in modules include LibreOffice general when they look at only Writer or only Calc shortcuts. Actual Results: Users don't see assigned LibreOffice general shortcuts when they look at only Writer/Calc/etc. shortcuts in Customize dialog Expected Results: Users should see assigned LibreOffice general shortcuts when they look at only Writer/Calc/etc. shortcuts in Customize dialog Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: bfca51d9035000e518e4938ceb145cb92cc17b1f CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded
Created attachment 181948 [details] Screenshot True, this information is missing in both direction. The idea is to overwrite general shortcuts in the modules, but OTOH you should at least know what is assigned. Could imagine a gray font color or italic font style.
The underlying concept of shortcuts is weak, see bug 115052 and the UI has not been reworked yet similar to the other tabs; some suggestions in bug 115527. And bug 83548 as well as bug 66298 report the same issue. *** This bug has been marked as a duplicate of bug 66298 ***