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

Heiko Tietze <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
                   |.freedesktop.org            |tion.org,
                   |                            |mentoring@documentfoundatio
                   |                            |n.org
     Ever confirmed|0                           |1
            Summary|Option to Disable Overwrite |Warning when the overwrite
                   |Mode (Insert Key)           |mode is enabled for the
                   |                            |first time
             Status|UNCONFIRMED                 |NEW
           Keywords|needsUXEval                 |difficultyMedium, easyHack,
                   |                            |skillCpp

--- Comment #4 from Heiko Tietze <[email protected]> ---
We discussed the topic in the design meeting.

While switching between insert/overwrite is standard behavior not every casual
user is aware of the classic workflow, in particular on macOS. Microsoft
blocked overwrite completely by adding an option with the default off. 

However, as LibreOffice users are typically more tech-affine we suggest not to
follow this example but add a confirmation dialog that is shown the first time
overwrite is activated (except per statusbar). It would tell the user "By
pressing the insert button you switch between the insert and the overwrite mode
indicated by a block caret. An active overwrite mode is also shown in the
statusbar. Do you want to enable it now? [Yes/No] /p (This dialog will not show
up again.)", ideally with an image similar to the tip-of-the-day. The dialog
must not close on accidental key press so the initial focus needs to be apart
the buttons.

Tentative code pointer
https://opengrok.libreoffice.org/xref/core/vcl/source/control/edit.cxx?r=5c156156#1685

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to