DeeJanuzandClaude Opus 5.5 c3785bb46e Floating windows: keep KWin's placement memory out ...

KWin's PlacementTracker keeps each window's geometry, full screen and
maximized state per layout of the outputs, and puts windows back when a
layout it has seen comes back. A spare output resizes after its window,
so resizing a floating window back to an earlier size (or changing its
scale, or full screen) made the window and its output flip forever, and
floating or docking one window could move others onto or off a spare.

The KWin script now keeps where each window belongs, reports nothing
while KWin changes the outputs, and on screensChanged puts floating
windows back (and the screens' windows when only spares changed),
cancelling KWin's requests before the app sees them. A size asked for is
held for a second against late answers.

With that: a launched app and a profile get their remembered scale back,
scale steps keep the size in pixels, ft-floatd waits for the end of an
edge resize before resizing the output (KWin cancels the resize on any
output change), a window taken over after a restart keeps its app and
panel density, and `ft-float float ID` asks the script for the window's
current place.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-01 08:50:38 -06:00

..

frametop-float.js

Floating windows: keep KWin's placement memory out

2026-10-01 08:50:38 -06:00

ft_apps.py

Launch apps floating, remember where they floated, and Launch as Standalone

2026-09-30 22:20:36 -06:00

ft_floatd.py

Floating windows: keep KWin's placement memory out

2026-10-01 08:50:38 -06:00

ft-float

Launch apps floating, remember where they floated, and Launch as Standalone

2026-09-30 22:20:36 -06:00

ft-float-apps

Launch apps floating, remember where they floated, and Launch as Standalone

2026-09-30 22:20:36 -06:00

ft-floatd

Add ft-floatd and the frametop-float KWin script

2026-09-29 23:20:26 -06:00