https://bugs.kde.org/show_bug.cgi?id=141968
Noah Davis <noaha...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |noaha...@gmail.com
--- Comment #6 from Noah Davis <noaha...@gmail.com> ---
The quickest solution would be to tell app devs to limit the shortcuts within
the apps that define the shortcuts, but then every app that naively implements
a global shortcut would still have this problem and apps might have slightly
different solutions for achieving the same end.
Something to consider is how the excessive global shortcut activation are being
triggered. In the case of the original report, auto repeat is what causes the
issue. Since KGlobalAccel's API uses QActions to register events, maybe we
could make something like `action->setAutoRepeat(false)` work? It could make it
so you have to release the shortcut sequence keys before it can be triggered
again. Auto repeat couldn't be disabled by default since there's no way to
determine whether an app dev explicitly set auto repeat on or left it at the
default value. At least it wouldn't require every app to implement their own
solution. It might not completely solve the problem, but it might solve most
issues caused by user input.
We could probably rate limit the processing of global shortcuts via timers.
However, how long or short the timer should be would probably be highly
dependent on the app and what the global shortcut does. There could be a global
shortcut that benefits from being able to be activated rapidly (e.g., volume
and brightness shortcuts). That once again means apps have to share some
responsibility for their behavior. Even 0ms timers might at least help with
compressing events created in rapid succession, but probably wouldn't solve the
issue. If we went this route, perhaps the behavior could be configurable by app
devs with the default being a behavior we generally consider safe?
--
You are receiving this mail because:
You are watching all bug changes.
