kwin/autotests/integration/effects/CMakeLists.txt

if (XCB_ICCCM_FOUND)
    integrationTest(NAME testTranslucency SRCS translucency_test.cpp LIBS XCB::ICCCM)
    integrationTest(NAME testSlidingPopups SRCS slidingpopups_test.cpp LIBS XCB::ICCCM)
    integrationTest(NAME testShadeWobblyWindows SRCS wobbly_shade_test.cpp LIBS XCB::ICCCM)
endif()
integrationTest(NAME testFade SRCS fade_test.cpp)
integrationTest(WAYLAND_ONLY NAME testEffectWindowGeometry SRCS windowgeometry_test.cpp)
Ensure that EffectsHandlerImpl::slotClientShown is only invoked once per Window Summary: This fixes a regression introduced with a1afeded6ae63e47d39fc08480e929c0451c51e8. The connections were setup every the windowShown signal got emitted. This caused effects to get multiple singals and start multiple animations which then do not get cancelled correctly. The incorrect behavior was most visible in the translucency effect which did not cancel the move animation and the window stayed translucent. BUG: 366081 Test Plan: New test case which simulates the behavior of the translucency effect. Reviewers: #kwin, #plasma, sebas Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D2346 2016-08-03 14:12:23 +00:00			`if (XCB_ICCCM_FOUND)`
			`integrationTest(NAME testTranslucency SRCS translucency_test.cpp LIBS XCB::ICCCM)`
[autotests/effect] Add test case for Sliding Popups effect The test case loads the sliding popups effect and the scale in effect which also operates on added windows. As the test case shows depending on the sequence how the effects are loaded, the window gets animated by both effects (wrong) oor only sliding popups. CCBUG: 336866 2016-10-30 10:27:38 +00:00			`integrationTest(NAME testSlidingPopups SRCS slidingpopups_test.cpp LIBS XCB::ICCCM)`
Sanity check WindowQuad before trying to create a grid out of it Summary: When one uses: * breeze as of 5.12 * wobbly windows * shaded window * a distribution building with assert enabled and starts to move a shaded window, KWin asserts. The root cause for this is that WindowQuad::makeSubQuad has an assert for y1 being smaller than y2. With the combination listed above this is not guaranteed. For the left shadow quad the y1 and y2 are identical and thus trying to split it, results in the assert condition. The problem of the shadow quad having an invalid size might be addressed as well with D10811. Due to that the generation of the quads is not touched. Instead a sanity check is introduced to not try to split already invalid sized quads. BUG: 390953 FIXED-IN: 5.12.3 Test Plan: Added unit test hit the assert, now doesn't hit it any more Reviewers: #kwin, #plasma Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D11015 2018-03-04 10:23:28 +00:00			`integrationTest(NAME testShadeWobblyWindows SRCS wobbly_shade_test.cpp LIBS XCB::ICCCM)`
Ensure that EffectsHandlerImpl::slotClientShown is only invoked once per Window Summary: This fixes a regression introduced with a1afeded6ae63e47d39fc08480e929c0451c51e8. The connections were setup every the windowShown signal got emitted. This caused effects to get multiple singals and start multiple animations which then do not get cancelled correctly. The incorrect behavior was most visible in the translucency effect which did not cancel the move animation and the window stayed translucent. BUG: 366081 Test Plan: New test case which simulates the behavior of the translucency effect. Reviewers: #kwin, #plasma, sebas Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D2346 2016-08-03 14:12:23 +00:00			`endif()`
[effects] Handle windowShown and windowHidden in fade effect Summary: For Wayland windows we can have a sequence of window unmapped (windowHidden signal) followed by a windowClosed way later when the application quits. This is for example the case with menus. The result of this was that the fade out animation triggered when the application quit showing all the already closed menus again. This change implements a windowShown and windowHidden handler and triggers the fadeIn/Out animation on it. If the window gets shown again the existing fadeOut animation gets cancelled, so that it can run again. If a window gets closed for which a fade out animation has been run already, it's not triggered again, thus ensuring that we don't see zombie windows. CCBUG: 372622 Reviewers: #kwin, #plasma_on_wayland, hein Subscribers: plasma-devel, kwin Tags: #plasma_on_wayland, #kwin Differential Revision: https://phabricator.kde.org/D3419 2016-11-18 14:27:34 +00:00			`integrationTest(NAME testFade SRCS fade_test.cpp)`
[effects] Delay creation of EffectFrames in WindowGeometryEffect Summary: Without Xwayland KWin starts so fast that the creation of the EffectFrame triggers a crash in the Wayland integration as the KWin internal connection isn't fully setup. To workaround this crash the creation of the EffectFrame is delayed till the first usage. It doesn't make sense to try to fix the actual crash as it would require to defer the creation of all Effects. Test Plan: New test case added which crashes without this fix. Reviewers: #kwin, #plasma Subscribers: plasma-devel, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D8821 2017-11-14 19:12:57 +00:00			`integrationTest(WAYLAND_ONLY NAME testEffectWindowGeometry SRCS windowgeometry_test.cpp)`