6b38b03724
When a window that is on a different virtual desktop than the current one gets activated, the current behavior is that the active virtual desktop will be switched to the one the activated window is on. This may seem reasonable for a scenario where the user explicitly intends to activate an existing window on a different desktop. However, the following scenario is also (perhaps even more?) common: When an application responds to a launch command by requesting to activate an existing instance instead of opening a new one (such as Firefox or KDE System Settings), an existing window on any desktop will get activated even when what the user had in mind was opening a new window (on the desktop they are currently in). This means that opening an application, such as following a URL or accessing a system setting, unexpectedly results in the user being teleported to a different virtual desktop. This can be very irritating. The more expected behavior for these users would be to have windows always open on the desktop where they are called from. That's is what this commit adds as a new option. BUG: 438375 FIXED-IN: 5.26 |
2 years ago | |
|---|---|---|
| LICENSES | 2 years ago | |
| autotests | 2 years ago | |
| cmake/modules | ||
| data | ||
| doc | 2 years ago | |
| kconf_update | ||
| src | 2 years ago | |
| tests | 2 years ago | |
| .clang-format | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .kde-ci.yml | ||
| CMakeLists.txt | 2 years ago | |
| CONTRIBUTING.md | ||
| KWinDBusInterfaceConfig.cmake.in | ||
| Mainpage.dox | ||
| README.md | ||
| logo.png | ||
| plasma-kwin_wayland.service.in | ||
| plasma-kwin_x11.service.in | ||
README.md
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.