[Libreoffice-ux-advise] [Bug 148258] Regaining user control over keyboard customization

[bugzilla-daemon at bugs.documentfoundation.org]

https://bugs.documentfoundation.org/show_bug.cgi?id=148258

--- Comment #6 from Vince <vreher at cox.net> ---
(In reply to Heiko Tietze from comment #5)

> We have plenty of tickets around keyboard customization, see bug 41560 about
> the customization and bug 107243 locale issues. The request here is rather
> about mnemonics (alt+accelerator, bug 146174), which is different to what is
> assigned to UNO commands. 

This bug and the bugs I mentioned (bug 49091, bug 53190, bug 93402, bug 146174)
should be added to meta bug 41560.

The request here is NOT simply about mnemonics but about the ability to
override those mnemonics via keyboard customization. We have been able to do
this for years until https://gerrit.libreoffice.org/c/core/+/122926. Part of my
patch addresses that in a rather unsubtle way, so I do not expect that part to
be accepted as is.

The request is also about reinstating a whole range of keystrokes for
customization that were pre-emptively removed many years ago for interactive
table sizing functions. The other part of my patch fixes that, while providing
a method to regain access to those functions even when the keystrokes are
reassigned.

> Some of the shortcuts are hard-coded. For example pressing return adds a
> paragraph break, arrow down / page down scrolls by a certain amount of lines
> etc. Some of these hard-wired shortcuts lead to the fact that you cannot
> customize this shortcut. An example is KEY_F1 and .uno:HelpIndex - F1 is
> blocked, perhaps because it's used in debug scenarios. Or for other reasons,
> see comment at MenuBarManager::FillMenuManager().

Return, Arrow Down, and Page Down all appear to be customizable. While
customization of Return is ignored, it is successful for the other keystrokes.

The keystrokes that are listed in the customization dialog but are greyed out
are are the ones reserved by vcl (see ReservedKeys in
vcl/source/app/svapp.cxx). While I have been able to see how vcl uses most of
the keys listed, I cannot figure out why vcl reserves Shift+Control+[0-9].

> The point is that blocking shortcuts for some reasons affects usability. We
> should eliminate that one by one. And my personal pet in this regard, bug
> 115052, should improve the UI anyway.

Interesting bug. It all boils down to scan codes and how to best to give them a
symbolic name.

> Back to the question... there is none. Suggest to resolve this ticket as
> INVALID. Or have I missed the point?

You can deduce that I completely disagree :)

-- 
You are receiving this mail because:
You are on the CC list for the bug.