On Thursday 5 September 2024 14:22:54 BST you wrote:

Since I upgraded to KDE Frameworks 6 I have observed some rather unwanted window behaviours.

1. Window Interaction with Gkrellm

DESIRED BEHAVIOUR:
==================
I have Gkrellm started up by Plasma at login and placed at the top left of the screen. I can't remember where/how I set this up, but at least it is still respected by KDE 6. I've always set Gkrellm via its Configuration > General > Properties with:

+ Set sticky state

+ Set window type to be a dock or panel

This allowed the following interaction with other application windows:

- Other windows would launch without overlapping the Gkrellm window. On an otherwise empty desktop they would be placed on the right of it.
- When a window was maximised it did not extend sideways to cover the whole screen beyond the position of the the Grkellm.
- When I dragged a window to force it to infringe the boundary of the
Gkrellm window, the Gkrellm would overlap the dragged window.

UNDESIRED BEHAVIOUR:
===================
With KDE Frameworks 6, Gkrellm is not recognised/respected fully as a dock panel:

Other application windows will maximise to the full width of the screen and be overlapped by Gkrellm. When the maximised window is a terminal, this
can be quite unhelpful.

If I unset Gkrellm as a dock, then when I launch some application window Gkrellm will be overlapped indiscriminately.

I tried playing with various Gkrellm and KDE window settings, but I can't
get it to interact with other windows in KDE 6 as it did in KDE 5.

I seem to have overcome this problem!

The first time I started Plasma/KDE6 I noticed the Gkrellm was placed in the middle of the screen. I dragged it to the top left, where I want it to be launched at startup. This happened a number of times and at some point I closed it down and restarted it to make sure it will retain its position on
the screen and by mistake, IIRC, I started a second Gkrellm instance at the same time. Then I closed the previous Gkrellm window.

Well, whatever were the settings of that 2nd Gkrellm window meant it was never recognised as a dock and was being under/overlapped by other applications. Today I started again a second Gkrellm window instance, which I noticed was behaving correctly as a dock! o_O

I closed the previous misbehaving instance, moved the second Gkrellm window in its place and restarted Plasma. This proved the Gkrellm which now launched at start up worked correctly as a dock. :D

I can't claim to understand this, but happy with the result all the same. -----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmby8q0ACgkQseqq9sKV ZxlDOhAA41MrgGew4+qGxBwB0n6Nsg/L/DnsqQA7l6Kbuqh5LqYijm8UqE9p1Z0l ca1bBgTBjGewhNhPiqv6QhfUgNNvmJ3XUJBDJ0flb8e4dLUlH8byRuw7F9AmHoC2 cath7105S6g8+nTt2AYRizlsHeLmW11Jl3/B83Qe8cOKJedbDm0QyT/ddCc/MXih CP1huo3d5hrPgDiflLqfD4arVWZpxbpUmCGzRVCrOvl5dmQsiKXgywNXgDCUZsJs rwlWGTj+NeAUtna/u/TnTuxCz+wJmaq43i1P2ci/8o+FmNC73qimuEEbe28v53mh XCM2dvrDh1l5OQ+qePYHrP086ITHCdyEvziszOif2p5hU62lNmZ/7xF2CTXzpSyE v7jtKSBsHznwZ2aRPSHfDneYtkvb4vA0+N77DSFBDWkV1FEYFY0AoCKoz0IBPJzc t6GeAw6QGjtBf1N+819WPadPL6N71rc88XpK1PHTh9+UQRqUed4iFDZUBRlqLA80 Km78LN0keO6TXKGD5+YxAFq84uLXJk3c5iHYOLim9Wxt5+rHmURROlDZexf21C+v yHUOkaX2JoWkiUa6TSSmJDOXiQVAAzxGF+xtQYqs6Wz9sk2h6ha+EFLqvqB5mb3L IMwJPPNU0VhwyGluO77P37/I0xY/Au0osf6c+W83wMfgp03zYz8=
=RywE
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Since I upgraded to KDE Frameworks 6 I have observed some rather unwanted window behaviours.

1. Window Interaction with Gkrellm

DESIRED BEHAVIOUR:
==================
I have Gkrellm started up by Plasma at login and placed at the top left of the screen. I can't remember where/how I set this up, but at least it is still respected by KDE 6. I've always set Gkrellm via its Configuration > General > Properties with:

+ Set sticky state

+ Set window type to be a dock or panel

This allowed the following interaction with other application windows:

- Other windows would launch without overlapping the Gkrellm window. On an otherwise empty desktop they would be placed on the right of it.
- When a window was maximised it did not extend sideways to cover the whole screen beyond the position of the the Grkellm.
- When I dragged a window to force it to infringe the boundary of the Gkrellm window, the Gkrellm would overlap the dragged window.

UNDESIRED BEHAVIOUR:
===================
With KDE Frameworks 6, Gkrellm is not recognised/respected fully as a dock panel:

Other application windows will maximise to the full width of the screen and be overlapped by Gkrellm. When the maximised window is a terminal, this can be quite unhelpful.

If I unset Gkrellm as a dock, then when I launch some application window Gkrellm will be overlapped indiscriminately.

I tried playing with various Gkrellm and KDE window settings, but I can't get it to interact with other windows in KDE 6 as it did in KDE 5.

2. Kmail compose window
=======================
The kmail composer window launches at the same size as the main kmail window. If I shrink it down to a more manageable size, then next time I launch kmail the main window is as small as I had shrunk its composer window. In KDE 5 the kmail main window and composer window sizes were dealt as separate windows
with their own size settings. Now one seems to inherit the dimensions of the other.


Have you experienced anything similar? How could I revert this unwanted
window management behaviour to what KDE 5 window management was like?

PS. Extra bonus points for someone who can offer an explanation why kmail spellcheck suddenly started applying US English as opposed to the actual setting of British English. o_O

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmbZsK4ACgkQseqq9sKV ZxlvJhAA57vpOrPDmLLKS5s0ggGQZWnHGtNDgXd2ECcu13IFRjMt2uEQ/svOs/qD UtofVjQ678UQm1PE5jwPTitHB02uJcuc0QW6+ODa3AFpfbDGBnVAoG2MuDHLD7x/ RSQPOBK7EnvxP/nqElJboVt+QdHUVUEesXCX47PpLCdlpZKly9RSWUNQ7AKql0S/ qUfEb+o5vCvUnxyxY/nCA+n6/Gls0OZBPgQ9VvwilOJUO9HseKT51Lu5o1KQwOrN DgX9lIFoXwYe0w5HwTLjruQ/jw8aw1E5Dm63yc+/Q0c+xwoDFB96LynCY7Y/lJng a96pweoBGDjNiU3esmSH6eGPpGPT/0LdSDflg19qdGpi/NAZZEdv+k7GjBCAd2A0 u0yPQZ812cydIBrg8blafttbymyflUvb2BZmxagFig3dYfJq7QJlHzbHybv56y8A yeP5t9QFtiyN3W22lN5MH5uaQ/wJs35v/bjU5qX8+su7I7REK9KiguvRotsA8/oo 7kCT1xqKvdGcJdrJznZj9LD47W5N8kgVdhIkSgVTPTv90JnB+19jmkdzxPiNkmlT 4L6ildpeLwcR7NdICjcC7VP5Lp90hOAyrVrc+Rwnex0sGBGQMx9tZnVifwLryZAr ZaHYwmhJJ3/EXoDkmha63i3HZWeRcAJaC7OZ6adoP98Mgi2ABKM=
=/Ux8
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)