wilderjds/kwin - kwin - gitea-jacopods

Author	SHA1	Message	Date
David Edmundson	3604aaf74c	Close screen grabbing effect when screensaver starts Summary: The screenlock fails on X11 if it can't grab the keyboard. We can't nicely solve the generic case. We can solve the common case of a kwin effect being active. It's not critical, arguably not even desirable to have these effects persist after the screen is locked through an external trigger. We can just close the effect early. Key grabs have to be relased early before the close animation completes so that the locker doesn't have a race based on animation times. It's not ideal, but no worse than the current state for not much work. BUG: 234153 Test Plan: locked screen on a timer opened various effects Reviewers: #kwin, zzag Reviewed By: #kwin, zzag Subscribers: ngraham, zzag, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D20890	7 years ago
Martin Gräßlin	697ea3ae00	Delay query whether screenlocker is registered till WaylandServer is initialized If we try to query before WaylandServer created the KSldApp the service owner change is never delivered. Thus a delay till we know that the service is there on Wayland. On X11 the initialization can be done directly. To know when the WaylandServer is fully initialized an additional signal is added to WaylandServer.	10 years ago
Martin Gräßlin	490eaadb83	Turn ScreenLockerWatcher into a KWIN_SINGLETON It's created together with input, so that the input mechanismn already has a way to check whether screen is locked. Effects doesn't hold a member variable any more and instead uses the singleton instance.	10 years ago
Martin Gräßlin	d2a3a10802	Split ScreenLockerWatcher into dedicated source files Being able to monitor whether the screen is locked is useful not only to the effects system but overall in KWin. Thus to make it possible to use it from more locations as a first step it's moved into dedicated source files.	10 years ago