My KWIN fork where I work on features like per-output virtual desktops
Find a file
Vlad Zahorodnii 5fb5f1c92b autotests: Stabilize testWaylandSeat
TestWaylandSeat::sync() ensures that events and requests can't be
reordered after it. That is, it guarantees that

- events sent from the compositor will be processed by the client
  before sync() finishes
- requests issued by the client will be processed by the compositor
  before sync() finishes

WaylandSyncPoint relies on the fact that wl_display_sync()'s callback
and other wayland events will be processed in the same event queue.

But, it's not the case right now. The wl_callback belongs to the default
event queue and KWayland::Client::Seat belongs to a different queue.

If the default event queue is dispatched first, the WaylandSyncPoint may
emit the done signal too early.

In order to fix sync(), this change ensures that WaylandSyncPoint's
wl_callback uses the correct event queue.
2023-04-24 11:40:24 +00:00
autotests autotests: Drop testDontCrashNoBorder 2023-04-24 10:13:58 +00:00
cmake/modules Drop Qt6WaylandClientMacros.cmake fork 2023-04-23 18:18:34 +00:00
data Port to KF6 2023-02-28 18:30:26 +02:00
doc Add option to do nothing when activating window on another desktop 2023-04-14 19:06:21 +00:00
LICENSES Remove unused license file 2022-08-23 17:41:55 +02:00
po GIT_SILENT Sync po/docbooks with svn 2023-04-24 03:00:58 +00:00
src autotests: Stabilize testWaylandSeat 2023-04-24 11:40:24 +00:00
tests Remove some include_directories() 2023-03-23 14:37:48 +02:00
.clang-format Run clang-format 2022-03-25 13:25:15 +02:00
.gitignore Run clang-format 2022-03-25 13:25:15 +02:00
.gitlab-ci.yml ci: Bump to Qt 6.5 2023-04-22 08:11:15 +00:00
.kde-ci.yml Port to standalone kglobalacceld 2023-04-23 10:06:28 +02:00
CMakeLists.txt Drop Qt6WaylandClientMacros.cmake fork 2023-04-23 18:18:34 +00:00
CONTRIBUTING.md add more debugging information to CONTRIBUTING.md 2023-01-09 13:40:31 +00:00
KWinDBusInterfaceConfig.cmake.in Expose org.kde.kwin.ColorCorrect.xml dbus file 2022-01-05 01:33:01 +00:00
logo.png
Mainpage.dox
plasma-kwin_wayland.service.in Re-enable systemd managed kwin 2021-12-02 13:25:50 +00:00
plasma-kwin_x11.service.in [systemd] Fix X11 service file 2022-01-20 16:18:48 +00:00
README.md doc: modernise HACKING -> CONTRIBUTING guidelines and information 2021-08-31 22:10:58 +00:00

KWin

KWin is an easy to use, but flexible, composited Window Manager for Xorg windowing systems (Wayland, X11) on Linux. Its primary usage is in conjunction with a Desktop Shell (e.g. KDE Plasma Desktop). KWin is designed to go out of the way; users should not notice that they use a window manager at all. Nevertheless KWin provides a steep learning curve for advanced features, which are available, if they do not conflict with the primary mission. KWin does not have a dedicated targeted user group, but follows the targeted user group of the Desktop Shell using KWin as it's window manager.

KWin is not...

  • a standalone window manager (c.f. openbox, i3) and does not provide any functionality belonging to a Desktop Shell.
  • a replacement for window managers designed for use with a specific Desktop Shell (e.g. GNOME Shell)
  • a minimalistic window manager
  • designed for use without compositing or for X11 network transparency, though both are possible.

Contributing to KWin

Please refer to the contributing document for everything you need to know to get started contributing to KWin.

Contacting KWin development team

  • mailing list: kwin@kde.org
  • IRC: #kde-kwin on irc.libera.chat

Support

Application Developer

If you are an application developer having questions regarding windowing systems (either X11 or Wayland) please do not hesitate to contact us. Preferable through our mailing list. Ideally subscribe to the mailing list, so that your mail doesn't get stuck in the moderation queue.

End user

Please contact the support channels of your Linux distribution for user support. The KWin development team does not provide end user support.

Reporting bugs

Please use KDE's bugtracker and report for product KWin.

Guidelines for new features

A new Feature can only be added to KWin if:

  • it does not violate the primary missions as stated at the start of this document
  • it does not introduce instabilities
  • it is maintained, that is bugs are fixed in a timely manner (second next minor release) if it is not a corner case.
  • it works together with all existing features
  • it supports both single and multi screen (xrandr)
  • it adds a significant advantage
  • it is feature complete, that is supports at least all useful features from competitive implementations
  • it is not a special case for a small user group
  • it does not increase code complexity significantly
  • it does not affect KWin's license (GPLv2+)

All new added features are under probation, that is if any of the non-functional requirements as listed above do not hold true in the next two feature releases, the added feature will be removed again.

The same non functional requirements hold true for any kind of plugins (effects, scripts, etc.). It is suggested to use scripted plugins and distribute them separately.