https://bugs.kde.org/show_bug.cgi?id=527445
Méven <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi |t/c41f62dcc6002e095969b142a |t/fb75a2825021d944c2ff9c761 |bdc56459d27a028 |512bbc6f73d5195 --- Comment #10 from Méven <[email protected]> --- Git commit fb75a2825021d944c2ff9c761512bbc6f73d5195 by Méven Car. Committed on 29/10/2026 at 11:44. Pushed by meven into branch 'master'. scripting: keep the screen that addPanel chose for a new panel The "Default Panel" template and other layout scripts add a panel through ShellCorona::addPanel(), which puts it on the active screen. The script engine then wrote lastScreen=0 to the panel configuration and restored it. Since the screen of a containment is read from lastScreen, the panel opened on the first screen after a restart, on top of the panel already there. The script engine now writes the screen that addPanel() chose. The shell autotests are built without the scripting engine. shelltest-scripting builds shelltest with it and runs the case for a panel that a script adds. M +28 -1 shell/autotests/CMakeLists.txt M +38 -0 shell/autotests/shelltest.cpp M +2 -4 shell/scripting/scriptengine.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/fb75a2825021d944c2ff9c761512bbc6f73d5195 -- You are receiving this mail because: You are watching all bug changes.
