Bug 127981 - can't disable f1 shortcut to open libre office help
Summary: can't disable f1 shortcut to open libre office help
Status: RESOLVED DUPLICATE of bug 106245
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.1.2 release
Hardware: x86-64 (AMD64) All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
Depends on:
Blocks:
 
Reported: 2019-10-06 09:20 UTC by thinkedsfoxe
Modified: 2019-10-06 16:22 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
can't change shortcut F1. customize keyboard menu. (7.13 KB, image/png)
2019-10-06 09:23 UTC, thinkedsfoxe
Details

Note You need to log in before you can comment on or make changes to this bug.
Description thinkedsfoxe 2019-10-06 09:20:55 UTC
step:tools>customize>keyboard
issue:that is F1 shortcut can't change. and F6,F10 or many gray out key.
this report spot on to > can't change F1 shortcut key.

summary:your want push key F2. if you mistake action to push key F2 with F1, this useless action.
libre open offline help or open browser libre office help.
yes, no need action, you can close it.
but all of the time with mistake action? every day? every time?

need change:
if can change this shortcut or disable open libre office help.
no stress with if mistake action.

example:can change shortcut F1 with program.> KDE dolphin. or KATE editor.
Comment 1 thinkedsfoxe 2019-10-06 09:23:27 UTC
Created attachment 154775 [details]
can't change shortcut F1. customize keyboard menu.

tools>customize>keyboard
Comment 2 V Stuart Foote 2019-10-06 16:22:15 UTC
The KEY_F1 is an internally reserved key [1] assigned in VCL to the .uno:HelpIndex command.  Not available to reassign as Customize action.

Duplicate of bug 106245 and remains => WF

The .uno:HelpIndex, aka 'LibreOffice Help' command receives an accelerator, and is available to assign as a keyboard shortcut.


[1]  https://opengrok.libreoffice.org/xref/core/vcl/source/app/svapp.cxx?r=73e3604f#84

*** This bug has been marked as a duplicate of bug 106245 ***