Using the Kwin QML scripting API, with many full-screen apps: - "window.fullscreen" reports false. - "window.size" reports less size than `Workspace.workspaceSize`. Samples: - prodeus.exe: fullScreen: true - firefox: fullScreen: false: QSizeF(1836, 1080) vs QSize(1920, 1080) - dosbox-staging: fullScreen: false: QSizeF(1836, 1080) vs QSize(1920, 1080) - The Dark Mod: fullScreen: false: QSizeF(1836, 1080) vs QSize(1920, 1080) Since Kwin ditched the previous API, suddenly nothing works. And I can fix jeez.
It sounds like those windows are maximized with a panel on the left, and not actually fullscreen?
There is a panel on the left, but the window is fullscreen and the panel invisible. My hypothesis is that most full screen windows are started windowed, and inmediately go fullscreen being the change invisible to the naked eye. But the function only catches the first state when called from a signal, as there is no delay. But I haven't investigated it further yet.
Okay, if I make the script wait 100ms it tells the correct resolution. So I was right: "fullscreen" cannot tell the resolution if the window is being started, as first it goes windowed to fullscreen.
This only happens with the signal "windowAdded", but not with "windowActivated"