In the following "to select" means "click it with mouse" -- I didn't evaluate the behaviour of the dialog via shortcuts! The Problem: When I try to assign a shortcut to a macro via -> Tools -> Customize -> Keyboard -> selecting an unassigned key under "Shortcut Keys" -> then selecting a "Category" the first element in "Function" is highlighted automatically, but the "Modify" button remains inactive. Only if I select another "Function" the "Modify" button becomes active. Now I could select the first "Function" again to finally assign the key to it via "Modify". But this doesn't work if there's only one "Function" in a "Category" (for example in category "LibreOffice Macros" -> "LibreOffice Macros" -> "pythonSamples" -> "TableSample"). Then I must select another key "Shortcut Key" instead for the "Modify" button to become active. Whenever I select another "Category" the "Modify" button becomes inactive again even though a "Function" (the first in the list) is selected automatically. The behaviour is independent of OpenGL usage. OpenCL cannot be activated on my installation (I can select but after the restart of LibreOffice it's inactive again). IMHO the "Modify" button should be active whenever an assignable "Function"-"Shortcut Key" pair is selected. Maybe there should not be an automatically selection of a "Function" on selecting a "Category", too. Best regards Ian
repro in Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: ac80ec817eb07c77a51bc0729985a473c734182e CPU threads: 12; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: en-GB Calc: CL
Dear Ian S., To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug