https://bugs.kde.org/show_bug.cgi?id=407498
--- Comment #1 from Alvin Wong <al...@alvinhc.com> --- By the way, I just ran `qtdiag` on Windows and it gives an empty string for manufacturer/model/serial number. Turns out they aren't implemented for Windows (and also macOS it seems)... should I say I'm not surprised. They can still be implemented, but at the end there needs to be a fallback in case those strings are really not available. So what we probably need are: 1. A way to generate an unique key for a monitor (probably by manufacturer/model/serial no.). 2. Somehow a fallback mapping to be used when the unique key doesn't work? Or would it be better to have Krita just ask the user to confirm the display profile mapping on startup and whenever the connected screens are changed (but only if the user have set a custom profile)? -- You are receiving this mail because: You are watching all bug changes.
