https://bugs.kde.org/show_bug.cgi?id=375921
Scott Harvey <bund...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bund...@gmail.com
--- Comment #30 from Scott Harvey <bund...@gmail.com> ---
(In reply to Eike Hein from comment #27)
> Re comment 24:
>
> Yup, I can agree with that. I think exposing SkipSwitcher in the API makes
> sense. I also think this makes an excellent "my first kwayland/kwin patch"
> Junior Job, since it's basically just taking a look at how the other Skip*
> stuff works and doing the same. Could be a nice way to onboard a new
> contributor.
I'm always open to being onboarded, but would like to clarify a few things
before bumbling around in the KWin code.
I think I understand this correctly... `skipTaskbar` and `skipPager` are
essentially just flags (in `NET::State`) that can be set on a window. Adding
`skipSwitcher` requires adding another available flag, more or less. KWin
itself doesn't directly act on these flags, but makes them available to other
applications. In other words, KWin doesn't control what shows up in a pager or
a switcher or a taskbar - it just reports which windows are eligible, according
to which `state` flags are set. It's up to the pager/switcher/taskbar to show
only the correctly-flagged windows.
Do I understand that correctly?
I apologize if this question is elementary to any of you. The internals of a
windowing system are new to me. I'm eager to help out (as always), but I'm also
not in the habit of wasting people's time with guesswork submissions.
Thanks.
--
You are receiving this mail because:
You are watching all bug changes.
