https://bugs.kde.org/show_bug.cgi?id=505945
--- Comment #5 from Dominik Kummer <[email protected]> --- But using the Display configuration's screen priority as screen index in Kwin reads reasonable on paper also. On all my devices with configured priorities this matching mechanism would make perfect sense to me. It's predictable that zero is always primary and so on. If the Kwin rules screen index is greater than available indices, it should always use the highest available index (least priority). Are there use cases where it doesn't work? -- You are receiving this mail because: You are watching all bug changes.
