Bug Hunting Session
Bug 83548 - Indication when a keyboard shortcut is set globally
Summary: Indication when a keyboard shortcut is set globally
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Customize-Dialog-Keyboard
  Show dependency treegraph
 
Reported: 2014-09-05 22:52 UTC by Yousuf Philips (jay) (retired)
Modified: 2017-08-09 11:22 UTC (History)
4 users (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 Yousuf Philips (jay) (retired) 2014-09-05 22:52:59 UTC
When adding a custom keyboard shortcut within an app, when that keyboard shortcut is already set in libreoffice global, there should be some type of indication that this shortcut shouldnt be used, possibly an asterisks next to the shortcut key, and there should be a dialog notice when attempting to assign a function to that shortcut key.
Comment 1 sophie 2014-09-25 13:57:00 UTC
Just a small feedback on this, I like the possibility to use a shortcut defined as global in a specific application, if I don't use the function behind. For example, I always define F4 to insert an image in Writer, because I never use datasource in Writer. So maybe an indication that the shortcut is globally used but not that it shouldn't be used. Sophie
Comment 2 Yousuf Philips (jay) (retired) 2014-09-25 17:50:19 UTC
Yes an indication that it is globally used when assigning it in an app/module, but not that it stop you from assigning it. Hopefully you wont need F4 to insert an image in the future, as in 4.4 it will be a button in the toolbar. :)
Comment 3 Robinson Tryon (qubit) 2014-12-29 22:12:42 UTC
Sounds reasonable.
Status -> NEW

UX: Thoughts on what the indicator should be?
Comment 4 Robinson Tryon (qubit) 2016-08-24 23:14:24 UTC Comment hidden (obsolete)
Comment 5 Heiko Tietze 2017-08-09 11:22:43 UTC
The request is part of the solution presented in bug 88896, being implemented during GSoC'17 projects.

Removing UX