Date: prev next · Thread: first prev next last
January 2019 Archives by date, by thread · List index


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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org
           Keywords|                            |difficultyBeginner,
                   |                            |easyHack, needsUXEval,
                   |                            |skillDesign, topicUI

--- Comment #4 from Heiko Tietze <tietze.heiko@gmail.com> ---
Apple has no Insert key and apparently no overtype mode. Microsoft provides an
option in a configuration dialog to toggle insert/override. 

We could implement a key additional to KEY_INSERT at editeng.cxx #1259.
Checking the world wide wisdom I'd say FN+Enter is the most often cited variant
(FN+backspace is the common delete, so it's somewhat natural). However, this
key would be hard-coded and wont be customizable. And to raise the difficulty
we do not have a function key defined yet (think it's possible when we restrict
it to macOS).

(Adding UX although it's a qualified easyhack to gather input. If a volunteer
wants to take this we can just go ahead.)

-- 
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.