SUMMARY Layout change OSD shows up on main screen, not where cursor is right now. Could it be changed to follow cursor to currently active screen? STEPS TO REPRODUCE 1. Hit Super+P or equivalent on keyboard. 2. OSD pops up on a screen which is set as main output, while my head expects it on screen where mouse cursor is right now. 3. Confusion, muscle memory tells me that it used to follow cursor, can't confirm though. I haven't used multiple screens for a while. OBSERVED RESULT OSD pops up on my "main" screen, then I have to move my mouse over to that screen, or use arrow keys. EXPECTED RESULT OSD should show up on currently active screen. Operating System: Arch Linux KDE Plasma Version: 5.25.90 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.10-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD RENOIR I am not sure what it was like before, however I am 100% sure, that behaviour of Application Dashboard used to behave how I describe, could be related if it's a regression.
https://invent.kde.org/plasma/kscreen/-/commit/cb4dd3b14fd4a3a15e0faf46feeae1e3d51fe401 should have not changed anything, looks like it was always on the primary screen as well. But I remember distantly that it used to show all on screen when you plugged a screen in, or is that also just imagination?
I agree that it makes sense
I am not sure to be honest, would have to download older image. It seems like a nice option to me regardless. That's how dashboard used to work before it was changed for some reason. Whoever reworked multiscreen for this version, nice work. It's appears more robust now.
*** Bug 428028 has been marked as a duplicate of this bug. ***
> https://invent.kde.org/plasma/kscreen/-/commit/cb4dd3b14fd4a3a15e0faf46feeae1e3d51fe401 should have not changed anything, looks like it was always on the primary screen as well. > But I remember distantly that it used to show all on screen when you plugged a screen in, or is that also just imagination? Yes, it used to. That's why there is a big (and now-redundant) infra with OsdManager and stuff. I think it would make sense to make it dynamically follow the cursor. For example, if cursor is on a screen that is physically disabled now, you won't be able to see the OSD. (yes, it is possible and totally legal to have a screen connected, enabled, but not showing your computer. for instance, monitor/tv may have multiple input sources, and user has just switched between them.)