https://bugs.kde.org/show_bug.cgi?id=488270
Zamundaaa <xaver.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/kwin/-/commit/7e450e42e5 |ma/kwin/-/commit/c3f4149bf0
|fcbe5d077fcfa473c65a8954c35 |2322011842ad48682c6deabedef
|d11 |c00
--- Comment #28 from Zamundaaa <xaver.h...@gmail.com> ---
Git commit c3f4149bf02322011842ad48682c6deabedefc00 by Xaver Hugl.
Committed on 23/01/2025 at 18:37.
Pushed by zamundaaa into branch 'Plasma/6.3'.
outputconfigurationstore: handle imperfect matches for outputs better
There are some situations where there can be multiple matches for a given
output, like
when two outputs with the same EDID ID but different EDID hashes or connector
names were
connected before and now only one of them is connected.
In these situations, we'd previously just pick the first match in the list,
even though
the other match is more precise; and that could end up changing the settings
for that
output. Once the second output is connected again, it would then get the wrong
settings.
To fix that, this commit only considers an entry in the config as a match if
there is only
one match for the relevant criteria. If there's multiple, then the search is
narrowed down
to take more crtieria into account, like the MST path or the connector name.
Related: bug 489457
(cherry picked from commit 7e450e42e5fcbe5d077fcfa473c65a8954c35d11)
M +90 -38 src/outputconfigurationstore.cpp
M +3 -4 src/outputconfigurationstore.h
https://invent.kde.org/plasma/kwin/-/commit/c3f4149bf02322011842ad48682c6deabedefc00
--
You are receiving this mail because:
You are watching all bug changes.
