Bug 95936 - Shortcut in tooltip not updated after changing the command's shortcut
Summary: Shortcut in tooltip not updated after changing the command's shortcut
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.1.0.0.alpha0+ Master
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Shortcuts-Accelerators Toolbars-Tooltips
  Show dependency treegraph
 
Reported: 2015-11-19 15:22 UTC by Juergen Funk (CIB)
Modified: 2019-01-18 09:33 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Juergen Funk (CIB) 2015-11-19 15:22:49 UTC
When you change the Shortcut Keys, then in the tooltip it is not update to the new one.
Go to Tools->Customise in the Customise-Dialog got to the Tab "Keyboard" for e.g. CTRL+F10 (that is the Non-printing Characters in Category "View") click "Delete" the Shortcut Key on CTRL-F10, select in Function "Non-printing Characters" go to CTRL-F5 and click "Modify", click "OK". Now when you go to the "Non-printing Characters"-Symbol in the toolbar, then it show always the old Shortcut, because the new one is working.
After a restart of LO you can see the new one.
Comment 1 A (Andy) 2015-11-19 22:05:03 UTC
Reproducible with LO 5.0.3.2, Win 8.1.
Comment 2 QA Administrators 2017-01-03 19:35:16 UTC Comment hidden (obsolete)
Comment 3 Juergen Funk (CIB) 2017-01-12 12:07:29 UTC
Sorry but at the moment i have not a build for testing, but i think that is not solved (no commit for that).

But when you mean this bug ist not important, you can close but i think that is not nice for the GUI. I have not the deep insight of the point of source, maybe  Easy-hack? 

Juergen
Comment 4 QA Administrators 2018-01-13 03:30:33 UTC Comment hidden (obsolete)
Comment 5 Juergen Funk (CIB) 2018-01-17 06:13:51 UTC
I have testing with master (aa02ed306f7c633bbffede16e44e8e736977ace4, debug), it is the same, no change for that.

Juergen
Comment 6 QA Administrators 2019-01-18 03:58:37 UTC Comment hidden (obsolete)
Comment 7 Juergen Funk (CIB) 2019-01-18 09:33:48 UTC
The current master b8e450a54936560cdac00ab4c70ef80c20cfaf99 still has the same behavior.

A other solution, when change then we hint the user, the app need an restart.



I think we should not be close this bug