https://bugs.kde.org/show_bug.cgi?id=377914
Martin Flöser <mgraess...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|REOPENED |RESOLVED
--- Comment #12 from Martin Flöser <mgraess...@kde.org> ---
I'm going to finally reset the status again and I'm urging to not change it
again.
In exchange I'm going to explain in more detail.
First of all let's have a look at what the help provides: "New windows get
activated only if no window is currently active or if they belong to the
currently active application. This setting is probably not really usable when
not using mouse focus policy."
We can see here that the help already restricts the usefulness of this setting.
Now let's look at it from a pure window manager perspective: The panel is not
the active application, in fact the panel is marked to never gain focus. When
clicking the app launcher a new window opens. It's a window just like any other
window. The window manager does not know that it is an app launcher. We
currently have a window activated and it's not Plasma, so the window won't get
focus and won't activate. Which in turn results in the app launcher closing
directly as it closes when losing focus.
As I said in a previous comment: this works exactly as advertised! This is
obviously an advance feature where we expect users to have knowledge about it.
I'm now going to quote KWin's mission statement:
"KWin is an easy to use, but flexible, composited Window Manger for Xorg
windowing systems 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. "
This setting is an advanced feature, we expect the user to have an
understanding of the feature when using it. We expect the user to understand
that this feature does not work with other elements in a perfect way - this is
even documented!
Now I understand that this is all fine, but when using a desktop this should
work. But for the desktop it's the same. Our tagline is "simple by default,
powerful when needed". By default all of this is working, the app launcher
opens, it gets focus. But Plasma let's you adjust the window manager, you can
set an advanced feature giving you the powerful when needed. Things might not
work as expected, but again Plasma gives you the features to help yourself.
With a simple window rule you can fine tune that the app launcher gets focus.
It is powerful when needed!
So is this here a bug? From KWin perspective: no, everything works as expected.
Fixing it without breaking the focus stealing prevention is nearly impossible.
>From an overall system perspective: maybe, but we are in the advanced feature
section and there is a good and simple workaround. So overall this is a clear
worksforme.
--
You are receiving this mail because:
You are watching all bug changes.
