public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE Frameworks 6 window management
Date: Fri, 06 Sep 2024 15:37:59 -0400	[thread overview]
Message-ID: <UHXIKWYC.FKIWPW3V.WNY6X75F@4CNY4KMC.H4N4UXYZ.QDKYTNXU> (raw)
In-Reply-To: <12513755.O9o76ZdvQC@rogueboard>

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?


  reply	other threads:[~2024-09-06 19: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 [this message]
2024-09-07 10:38                   ` Michael
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=UHXIKWYC.FKIWPW3V.WNY6X75F@4CNY4KMC.H4N4UXYZ.QDKYTNXU \
    --to=ostroffjh@users.sourceforge.net \
    --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