Customization of Del was requested on the ML [1]. The trick is to assign an action to "Delete Content" (thanks Piet for finding this) though it would be more transparent for the user when Del itself has a clear assignment in the first place (apparently to this command). [1] http://document-foundation-mail-archive.969070.n3.nabble.com/Adding-keyboard-shortcut-tc4254134.html
Heiko, could you write your suggestion in detail?
(In reply to Roman Kuznetsov from comment #1) > Heiko, could you write your suggestion in detail? Hi Heiko, Please elaborate it a bit more... Moving to NEW...
We need an UNO command in order to allow customization. More info in the referenced post to the mailing list.
Created attachment 168841 [details] Delete Contents command in the Customize dialog in current master This command exists, and it is assigned the Delete key on the generic application level since forever (okay, only checked LO 6.0.7 right now): officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu: <node oor:name=".uno:Delete" oor:op="replace"> officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu- <prop oor:name="Label" oor:type="xs:string"> officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu- <value xml:lang="en-US">Delete C~ontents...</value> officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu- </prop> It's just not very easy to find it, like finding any other command in our jungle of commands. I think this is basically NAB. Maybe a bit more documentation could be useful on the top right radio buttons in this dialog.
(In reply to Gabor Kelemen from comment #4) > This command exists... But the key is still hard-coded, or am I wrong? Guess the UNO command comes in addition.
(In reply to Heiko Tietze from comment #5) > (In reply to Gabor Kelemen from comment #4) > > This command exists... > > But the key is still hard-coded, or am I wrong? Guess the UNO command comes > in addition. I think the uno:Delete command has the Delete key assigned to it via Accelerators.xcu: https://opengrok.libreoffice.org/search?project=core&full=%22uno%3ADelete%22&defs=&refs=&path=officecfg&hist=&type=&xrd=&nn=1 So it's possible to change it in the Keyboard dialog, like OP asked on the Users ML. Changing the global shortcut of Delete Contents to (just for an example) Shift+Ctrl+D and unassigning the existing Writer-level command of Shift+Ctrl+D works as expected. This covers the editors, but not all dialogs, side bars (Gallery comes to mind) etc where it is explicitly handled by code. That was not asked for though, as far as I understand. All in all: feature wise -> NAB; but documentation (extended/normal tooltip) could be more detailed. Also the option to switch between generic shortcuts and application-specific ones (selected by default) could be made more prominent after an upcoming redesign of the whole tab (bug #115527 - also see similar requests bug # 83548 and bug #66298). Currently the extended help says: "Displays shortcut keys that are common to all %PRODUCTNAME applications." [1] while there is no default tooltip - setting something for that sounds actionable for the short term. [1] https://opengrok.libreoffice.org/xref/core/cui/uiconfig/ui/accelconfigpage.ui?r=5143de38#164 Cheers Gabor
Dear Heiko Tietze, 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