From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE Frameworks 6 window management
Date: Sat, 07 Sep 2024 11:38:38 +0100 [thread overview]
Message-ID: <22417340.EfDdHjke4D@rogueboard> (raw)
In-Reply-To: <UHXIKWYC.FKIWPW3V.WNY6X75F@4CNY4KMC.H4N4UXYZ.QDKYTNXU>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
On Friday 6 September 2024 20:37:59 BST Jack wrote:
> On 2024.09.06 11:12, Michael wrote:
>
> [snip ....]
>
> > The second problem I started this thread with, related to the Kmail
> > composer window inheriting the main Kmail window size and vice versa,
> > seems to occur because both windows are identified having the same
> > "kmail org.kde.kmail2" named Class. I played around with various
> > properties, like window type and what not, but I have not been able
> > to add a separate window size for the composer alone without
> > affecting the main Kmail window. If anyone comes up with a working
> > solution please chime in!
>
> I haven't been following very closely, but it sound like one approach
> would be to have one of the windows use a different name Class. Might
> it be worth raising as an issue for kmail itself?
I understood the Window Class of an application is hard coded, all a user like
me can do is select it. I can't claim to understand this correctly, or
furthermore understand how the X11 properties transpose over to a Wayland
desktop:
https://www.x.org/releases/current/doc/xorg-docs/icccm/
icccm.html#WM_CLASS_Property
Either way, the good news is others have been annoyed similarly by this
behaviour and raised a bug report. It seems to be a regression bug:
https://bugs.kde.org/show_bug.cgi?id=484327
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-09-07 10:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 13:22 [gentoo-user] KDE Frameworks 6 window management Michael
2024-09-05 14:34 ` Dale
2024-09-05 16:59 ` Michael
2024-09-06 1:02 ` Dale
2024-09-06 8:43 ` Michael
2024-09-06 11:04 ` Dale
2024-09-06 11:28 ` Michael
2024-09-06 11:40 ` Dale
2024-09-06 15:12 ` Michael
2024-09-06 19:37 ` Jack
2024-09-07 10:38 ` Michael [this message]
2024-09-05 20:30 ` Re gkrellm: Was: " Jack
2024-09-05 20:41 ` Michael
2024-09-24 17:11 ` [gentoo-user] " Michael
2024-09-24 22:54 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=22417340.EfDdHjke4D@rogueboard \
--to=confabulate@kintzios.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox