https://bugs.kde.org/show_bug.cgi?id=341201
Martin Gräßlin <mgraess...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |http://commits.kde.org/kwin
| |/57b11f84296b69944b907a89d4
| |03dc50d36a75dc
Resolution|UPSTREAM |FIXED
--- Comment #11 from Martin Gräßlin <mgraess...@kde.org> ---
Git commit 57b11f84296b69944b907a89d403dc50d36a75dc by Martin Gräßlin.
Committed on 15/02/2016 at 14:53.
Pushed by graesslin into branch 'master'.
[backends/drm] Use an InputEventFilter to reenable outputs
So far the DrmOutput connected to all input events when going into
power saving. As we now have the input filters it's better to just
install a filter when an output goes into powersave and remove the
input filter again when all outputs are enabled again.
To make this work InputRedirection gains a new method to add a new
filter as the first filter. This is a potentially dangerous method
as it allows to have a filter before LockScreenFilter gets the
events. But in case of DPMS it's something we actually want.
A nice new feature possible with the input filter is that we can
filter out the event which re-enables the outputs. Thus when getting
on a system with output off and screen locked, the first key hit
doesn't go to the lock screen.
Reviewed-By: Bhushan Shah
Fixed-in: 5.6.0 (Wayland-only)
M +76 -14 backends/drm/drm_backend.cpp
M +25 -1 backends/drm/drm_backend.h
M +5 -0 input.cpp
M +9 -1 input.h
http://commits.kde.org/kwin/57b11f84296b69944b907a89d403dc50d36a75dc
--
You are receiving this mail because:
You are watching all bug changes.
