https://bugs.kde.org/show_bug.cgi?id=470105
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|accessibility, efficiency |
Resolution|--- |INTENTIONAL
Status|REPORTED |RESOLVED
CC| |n...@kde.org
--- Comment #1 from Nate Graham <n...@kde.org> ---
> troublesome if you are reading documents, scripting, etc
That's typically why content apps hide the cursor when they're interacted with
using the keyboard. If they don't... they should! This is much nicer than a
timer system to hide the cursor after some period of inactivity; when I start
navigating via the keyboard in a document reader app like Okular, I'd want the
cursor hidden *now*, not in five minutes!
It sounds like you're using a piece of 3rd-party software to workaround such
issues in apps. I can understand that you found a solution that works for you,
but as you've observed, it won't work on Wayland.
In general, it's best when issues in apps are fixed in apps, rather than worked
around elsewhere. I think it's time for you to report bugs against the apps
that don't behave as you'd like. That way eventually those issues can be fixed
and then you won't need this workaround. And the issues will ultimately be
fixed for others, as well.
Beyond that, the requested behavior is probably possible to implement via a
KWin script, but I don't think there's any interest in adding it as a 1st-party
supported feature, sorry/
--
You are receiving this mail because:
You are watching all bug changes.
