https://bugs.kde.org/show_bug.cgi?id=501654
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from [email protected] --- I'd like to implement this and am looking for a nod on the approach before opening an MR. Current state: the position is hardcoded in KWin's `Placement::placeOnScreenDisplay()` (src/placement.cpp) — horizontally centered, 2/3 down the screen. plasmashell's `OsdWindow` only sets the plasma-surface OSD role, so KWin decides placement on both Wayland and X11, and one option there would cover all OSDs uniformly (volume, brightness, keyboard layout, ...). Proposed design: - A kwinrc option read by placeOnScreenDisplay(), since KWin is the consumer - Values as screen anchors (corners, edge midpoints, center) rather than free pixel coordinates — same UX as the notification popup position picker in the Notifications KCM, which comment 1 already drew the analogy to. I'd reuse that selector-style widget for consistency - Default preserves today's behavior exactly, so nothing changes for existing users Open questions: 1. Config/UI home: is a kwinrc option with the UI in KWin's own KCM acceptable, or would you rather see it next to the OSD-related toggles in Workspace Behavior → General Behavior (which would mean that KCM writing kwinrc)? The old attempt (kwin!217) stalled precisely on this plumbing question. 2. Any objection to anchors-only (no arbitrary coordinates, no per-OSD-type positions)? Requests like showing the OSD on all monitors (bug 507695) would stay out of scope I'd include integration tests in KWin's autotest suite alongside the placement change. If this direction sounds right, I'll open the MR against kwin master. -- You are receiving this mail because: You are watching all bug changes.
