Bug 88345 - Option to make mouse pointer disappear after typing with the keyboard
Summary: Option to make mouse pointer disappear after typing with the keyboard
Status: CONFIRMED
Alias: None
Product: kwin
Classification: Plasma
Component: wayland-generic (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
: 77062 118503 131483 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-08-28 23:19 UTC by Marius
Modified: 2023-09-18 19:29 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marius 2004-08-28 23:19:14 UTC
Version:            (using KDE KDE 3.3.0)
Installed from:    Debian testing/unstable Packages

Option to make mouse disappear then using keyboard. Why show the cursor then it is not needed? This is implemented in konsole, but the global one would be handy.
Comment 1 Waldo Bastian 2005-03-31 00:05:20 UTC
It's globally available to application that wish to use it, konqueror uses it for example.
Comment 2 Marius 2005-04-02 23:05:04 UTC
Yes, it's globally available to _KDE_ application that wish to use it. But I have KDE desktop and Motif application and I can't use it.
Comment 3 Mikael Djurfeldt 2006-02-23 11:18:22 UTC
In my opinion, the mouse disappearance behaviour is naturally associated with the *desktop*---more so than with individual applications (even if some types of applications, like those showing full-screen images, also might want to control this).

I was really surprised when I yesterday found out that there is no such setting in control center.

The user wants to be able to make the decision "I want the mouse to disappear if I don't use it" regardless of which window it sits over. This feature exists in Windows XP (not necessarily a good argument) and I remember that the Amiga had several open source tools for implementing this for the desktop.
Comment 4 Andreas Kling 2006-08-12 23:24:05 UTC
*** Bug 118503 has been marked as a duplicate of this bug. ***
Comment 5 Andreas Kling 2006-08-12 23:24:17 UTC
*** Bug 131483 has been marked as a duplicate of this bug. ***
Comment 6 Andreas Kling 2006-08-12 23:52:19 UTC
*** Bug 77062 has been marked as a duplicate of this bug. ***
Comment 7 g111 2006-08-14 11:43:06 UTC
*** This bug has been confirmed by popular vote. ***
Comment 8 greatbunzinni 2006-10-25 13:29:25 UTC
Isn't it possible to fix this behaviour? I thought that the cursor was never hidden when I typed because of some obscure config option which I missed somewhere. And by the way, if it is already possible to handle this on KDE applications and having in mind that, as it is easy to see, this feature is expected by whoever uses KDE, why not turn on the cursor hiding by default and then enable the applications to turn it off if they want?
Comment 9 Marius 2008-09-18 14:56:27 UTC
Found a work around http://packages.debian.org/sid/unclutter
Comment 10 g111 2008-09-18 15:29:15 UTC
unclutter does not work here as I would like it to behave. The mouse cursor can be hidden after a timeout but not on keypress. The man page gives the following note:

LIMITATIONS
The -keystroke option may not work (that is, the cursor will not disappear) with clients that request KeyRelease events. Games and Xt applications using KeyUp in their translation tables are most likely to suffer from this problem. The most feasible solution is to extend unclutter to use the XTest extension to get all keyboard and mouse events, though this of course requires XTest to be in the server too.
Comment 11 S. Burmeister 2010-06-15 09:10:50 UTC
This would be very useful for mobile devices since you do not want a mouse cursor on a touchscreen. So completely disabling it would be another variant of the "hide mouse cursor" issue.
Comment 12 Nate Graham 2020-09-29 22:30:32 UTC
Seems reasonable. We might be able to do this in plasma-integration, perhaps with some KWin work.
Comment 13 Harrison S 2021-08-14 23:02:26 UTC
I'd also like to request that this can be disabled globally, rather than be hard-coded by application. If this is addressed elsewhere I couldn't find it. Other DEs, and Windows, seem to take a global approach to this issue.