yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kwin/tests/CMakeLists.txt

39 lines
1.6 KiB
Text
Raw Normal View History

[kwin] Add a test application for testing size increment The test application can verify that KWin correctly interprets the WM_NORMAL_HINTS as described in ICCCM section 4.1.2.3 for the combination of min size, base size and size increment. Introduces an optional dependency to xcb-icccm library. It's optional as the last time we tried to use it build.kde.org didn't like it at all. Thus it should be possible to disable building this test app if the dependency is not found.
2014-01-30 14:28:12 +00:00
if (XCB_ICCCM_FOUND)
set(normalhintsbasesizetest_SRCS normalhintsbasesizetest.cpp)
add_executable(normalhintsbasesizetest ${normalhintsbasesizetest_SRCS})
Stop including KDE4_INCLUDES globally Depend on libraries specifically instead.
2014-03-18 16:53:22 +00:00
target_link_libraries(normalhintsbasesizetest XCB::XCB XCB::ICCCM KF5::WindowSystem)
[kwin] Add a test application for testing size increment The test application can verify that KWin correctly interprets the WM_NORMAL_HINTS as described in ICCCM section 4.1.2.3 for the combination of min size, base size and size increment. Introduces an optional dependency to xcb-icccm library. It's optional as the last time we tried to use it build.kde.org didn't like it at all. Thus it should be possible to disable building this test app if the dependency is not found.
2014-01-30 14:28:12 +00:00
endif()
Screenedge show support for Clients This provides a new protocol intended to be used by auto-hiding panels to make use of the centralized screen edges. To use it a Client can set an X11 property of type _KDE_NET_WM_SCREEN_EDGE_SHOW to KWin. As value it takes: * 0: top edge * 1: right edge * 2: bottom edge * 3: left edge KWin will hide the Client (hide because unmap or minimize would break it) and create an Edge. If that Edge gets triggered the Client is shown again and the property gets deleted. If the Client doesn't border the specified screen edge the Client gets shown immediately so that we never end in a situation that we cannot unhide the auto-hidden panel again. The exact process is described in the documentation of ScreenEdges. The Client can request to be shown again by deleting the property. If KWin gets restarted the state is read from the property and it is tried to create the edge as described. As this is a KWin specific extension we need to discuss what it means for Clients using this feature with other WMs: it does nothing. As the Client gets hidden by KWin and not by the Client, it just doesn't get hidden if the WM doesn't provide the feature. In case of an auto-hiding panel this seems like a good solution given that we don't want to hide it if we cannot unhide it. Of course there's the option for the Client to provide that feature itself and if that's wanted we would need to announce the feature in the _NET_SUPPORTED atom. At the moment that doesn't sound like being needed as Plasma doesn't want to provide an own implementation. The implementation comes with a small test application showing how the feature is intended to be used. REVIEW: 115910
2014-02-20 11:39:23 +00:00
# next target
set(screenedgeshowtest_SRCS screenedgeshowtest.cpp)
add_executable(screenedgeshowtest ${screenedgeshowtest_SRCS})
KWin::Application holdes a KSharedConfigPtr with the config This allows the integration tests to provide their own configuration as they need it. Setting the configuration should be done before invoking start()
2016-01-29 08:48:02 +00:00
target_link_libraries(screenedgeshowtest Qt5::Widgets Qt5::X11Extras KF5::ConfigCore KF5::WindowSystem ${XCB_XCB_LIBRARY})
[tests] Add a waylandclienttest application A small test application to use the Wayland Client classes. It opens a fullscreen Shell surface and reacts to input events: * q quits * left click toggles the background color animation * right click quits REVIEW: 119883
2014-08-21 10:57:50 +00:00
[tests] Only use KWayland in the waylandclienttest No need for Wayland::Client any more - KWayland encapsulates the usage.
2015-03-23 08:54:37 +00:00
if (KF5Wayland_FOUND)
[tests] Add a waylandclienttest application A small test application to use the Wayland Client classes. It opens a fullscreen Shell surface and reacts to input events: * q quits * left click toggles the background color animation * right click quits REVIEW: 119883
2014-08-21 10:57:50 +00:00
add_definitions(-DSOURCE_DIR="${KWIN_SOURCE_DIR}")
set(waylandclienttest_SRCS
waylandclienttest.cpp
)
add_executable(waylandclienttest ${waylandclienttest_SRCS})
[tests] Only use KWayland in the waylandclienttest No need for Wayland::Client any more - KWayland encapsulates the usage.
2015-03-23 08:54:37 +00:00
target_link_libraries(waylandclienttest Qt5::Core Qt5::Gui KF5::WaylandClient)
[tests] Add a waylandclienttest application A small test application to use the Wayland Client classes. It opens a fullscreen Shell surface and reacts to input events: * q quits * left click toggles the background color animation * right click quits REVIEW: 119883
2014-08-21 10:57:50 +00:00
endif()
Initial support for libinput Libinput is an optional dependency for getting low level input events. As opening the input devices requires root privs this is rather pointless in the current state. But there is a small added test app which can be executed with root privs to demonstrate the functionality. To properly get input events we need a wrapper like it's used in weston. So far the following is setup: * opening devices found by udev * forwarding keyboard events to InputRedirection * forwarding pointer button events to InputRedirection * forwarding pointer axis events to InputRedirection * signals emitted for pointer motion events Pointer motion events need some further work as they are provided as delta events. We need to track that and map them properly. Also missing are touch events due to me not having a touch screen. It should be fairly simple to setup the touch events, though. Also hotplugging of devices is not yet implemented.
2014-08-14 12:43:57 +00:00
if (HAVE_INPUT)
set(libinputtest_SRCS
libinputtest.cpp
${KWIN_SOURCE_DIR}/libinput/context.cpp
${KWIN_SOURCE_DIR}/libinput/connection.cpp
[libinput] Add a wrapper class Device for a libinput_device Summary: The Device class wraps all the information we can get from libinput about the device, like whether it's a keyboard, pointer, touch, etc. In addition some more information is queried to figure out how "useful" a device is. For a keyboard all alphanumeric keys are checked whether they exist, for a pointer all (normal) buttons are queried. All the information is exposed as Q_PROPERTY and used by the DebugConsole. The DebugConsole gained a new tab "Input Devices" which renders all devices and their properties in a tree view. When plugging in/out a device, the model gets reset, so it's always up to date. The new Device class can be used in future to configure the device, e.g. disable touch pad, set mouse acceleration, etc. Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1538
2016-05-04 11:42:26 +00:00
${KWIN_SOURCE_DIR}/libinput/device.cpp
Initial support for libinput Libinput is an optional dependency for getting low level input events. As opening the input devices requires root privs this is rather pointless in the current state. But there is a small added test app which can be executed with root privs to demonstrate the functionality. To properly get input events we need a wrapper like it's used in weston. So far the following is setup: * opening devices found by udev * forwarding keyboard events to InputRedirection * forwarding pointer button events to InputRedirection * forwarding pointer axis events to InputRedirection * signals emitted for pointer motion events Pointer motion events need some further work as they are provided as delta events. We need to track that and map them properly. Also missing are touch events due to me not having a touch screen. It should be fairly simple to setup the touch events, though. Also hotplugging of devices is not yet implemented.
2014-08-14 12:43:57 +00:00
${KWIN_SOURCE_DIR}/libinput/events.cpp
[libinput] Add dedicated logging category for libinput
2015-07-31 10:43:06 +00:00
${KWIN_SOURCE_DIR}/libinput/libinput_logging.cpp
Use Logind to open/close devices needed by libinput With libinput we have the problem that we need to have privileges to open the device files. In order to not need wrappers or suid bits, we use logind. This means that kwin_wayland has to be the session controler. A LogindIntegration is added to connect to logind and wrap the dbus calls. This is based on the logind integration done for ksld in ksmserver. The LogindIntegration is started by Workspace and the InputRedirection tries to become the session controller and starts the libinput integration only after this succeeded.
2014-08-15 07:30:08 +00:00
${KWIN_SOURCE_DIR}/logind.cpp
Move Udev into an own header and implementation For a DRM backend we also need Udev, so don't bundle with libinput.
2015-04-08 08:25:51 +00:00
${KWIN_SOURCE_DIR}/udev.cpp
Initial support for libinput Libinput is an optional dependency for getting low level input events. As opening the input devices requires root privs this is rather pointless in the current state. But there is a small added test app which can be executed with root privs to demonstrate the functionality. To properly get input events we need a wrapper like it's used in weston. So far the following is setup: * opening devices found by udev * forwarding keyboard events to InputRedirection * forwarding pointer button events to InputRedirection * forwarding pointer axis events to InputRedirection * signals emitted for pointer motion events Pointer motion events need some further work as they are provided as delta events. We need to track that and map them properly. Also missing are touch events due to me not having a touch screen. It should be fairly simple to setup the touch events, though. Also hotplugging of devices is not yet implemented.
2014-08-14 12:43:57 +00:00
)
add_executable(libinputtest ${libinputtest_SRCS})
[libinput] Support toggleTouchpad Summary: The LibInput::Device provides a way to enable/disable the device. This is used by the Connection to toggle all touchpad devices on/off when the touchpad key is pressed. For this KWin "steals" the global shortcuts from the touchpad kded. Detecting what is a touchpad is unfortunately not tivial. The code uses the following approach: * it's a pointer * it's not also a keyboard or touch screen * it's at least one of the following: ** supports multiple tap fingers ** supports disable while typing ** supports disable on external mouse If the code finds a touchpad and changes it's state successfully, it triggers the touchpadEnabledChanged on Plasma's osdService. Test Plan: Tested on notebook with toggle touchpad button Reviewers: #plasma Subscribers: plasma-devel Projects: #plasma Differential Revision: https://phabricator.kde.org/D1545
2016-05-06 10:28:07 +00:00
add_definitions(-DKWIN_BUILD_TESTING)
target_link_libraries(libinputtest Qt5::Core Qt5::DBus Libinput::Libinput ${UDEV_LIBS} KF5::ConfigCore KF5::GlobalAccel KF5::WindowSystem)
Initial support for libinput Libinput is an optional dependency for getting low level input events. As opening the input devices requires root privs this is rather pointless in the current state. But there is a small added test app which can be executed with root privs to demonstrate the functionality. To properly get input events we need a wrapper like it's used in weston. So far the following is setup: * opening devices found by udev * forwarding keyboard events to InputRedirection * forwarding pointer button events to InputRedirection * forwarding pointer axis events to InputRedirection * signals emitted for pointer motion events Pointer motion events need some further work as they are provided as delta events. We need to track that and map them properly. Also missing are touch events due to me not having a touch screen. It should be fairly simple to setup the touch events, though. Also hotplugging of devices is not yet implemented.
2014-08-14 12:43:57 +00:00
endif()
[tests] Tool to read the X11 shadow on a window Summary: This new helper tool allows to read the X11 shadow from a window and visualize the individual parts. Reviewers: #kwin Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D2101
2016-07-06 11:32:38 +00:00
add_executable(x11shadowreader x11shadowreader.cpp)
target_link_libraries(x11shadowreader XCB::XCB Qt5::Widgets Qt5::X11Extras KF5::ConfigCore KF5::WindowSystem)
Reference in a new issue Copy permalink