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

Stéphane Guillou (stragu) <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org,
                   |                            |stephane.guillou@libreoffic
                   |                            |e.org
           See Also|                            |https://bz.apache.org/ooo/s
                   |                            |how_bug.cgi?id=67807
                URL|                            |https://ask.libreoffice.org
                   |                            |/t/writer-make-mouse-cursor
                   |                            |-disappear-while-typing/359
                   |                            |22
            Version|unspecified                 |Inherited From OOo

--- Comment #3 from Stéphane Guillou (stragu) 
<[email protected]> ---
UX/Design team, what do you think? Is this something for LO or should it be the
role of the OS/DE?

- On Linux, a tool like xbanish could be used: https://github.com/jcs/xbanish
- Windows has Mouse properties > Pointer options > Hide pointer while typing:
https://www.howtogeek.com/766041/how-to-hide-your-cursor-while-typing-in-windows/
- on macOS, it seems to be the default:
https://apple.stackexchange.com/questions/71661/how-do-i-disable-hiding-of-the-mouse-pointer-while-typing-text
- with KDE and GNOME, it is done per app. See e.g.
https://www.reddit.com/r/kde/comments/15rvcfw/prevent_mouse_pointer_from_hiding_while_typing/
I just tested Gedit, GNOME Terminal and Firefox and they all hide the pointer
while typing, whereas Chromium, Gnumeric, Falkon and Thunderbird don't.

So I'd say it needs to be implemented and given as an option in Options >
LibreOffice > View, least for Linux.

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

Reply via email to