Date: prev next · Thread: first prev next last
March 2018 Archives by date, by thread · List index


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

Heiko Tietze <tietze.heiko@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|needsUXEval                 |difficultyBeginner,
                   |                            |easyHack, skillCpp
                 CC|libreoffice-ux-advise@lists |tietze.heiko@gmail.com,
                   |.freedesktop.org            |vstuart.foote@utsa.edu
            Summary|Indicate context-specific   |Remove "3 seconds to
                   |reserved keyboard shortcuts |add/delete col/row"
                   |in the customize dialog     |functions

--- Comment #16 from Heiko Tietze <tietze.heiko@gmail.com> ---
The recommendation of the design team to remove the weird function was accepted
in the ESC today. This should solve the actual problem, though it's not a call
for  hunting easter eggs. If similar issues with hard-coded key combinations
become a problem we have to decide how to proceed. Adjusted the summary
accordingly from the original "Indicate context-specific reserved keyboard
shortcuts in the customize dialog".

Destructive coding is per se easyhacking. Shouldn't be too hard to find the
respective code pointers.

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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.