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
signature.asc
Description: This is a digitally signed message part.
