From 41f66a37a19b92249a6c52bc68a711f477085e42 Mon Sep 17 00:00:00 2001 From: Alexander Lohnau Date: Sat, 21 Oct 2023 09:56:40 +0200 Subject: [PATCH] kscreenintegration: Do not use pointer in QMap as key Sorting bases om memory addresses doesn't make sense, also, we have proper sorting using std::sort in the readOutputConfig method --- src/kscreenintegration.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/kscreenintegration.cpp b/src/kscreenintegration.cpp index 1f7eeeab3d..abff82a5f8 100644 --- a/src/kscreenintegration.cpp +++ b/src/kscreenintegration.cpp @@ -53,7 +53,7 @@ QString connectedOutputsHash(const QList &outputs, bool isLidClosed) return QString::fromLatin1(hash.toHex()); } -static QMap outputsConfig(const QList &outputs, const QString &hash) +static QHash outputsConfig(const QList &outputs, const QString &hash) { const QString kscreenJsonPath = QStandardPaths::locate(QStandardPaths::GenericDataLocation, QStringLiteral("kscreen/") % hash); if (kscreenJsonPath.isEmpty()) { @@ -89,7 +89,7 @@ static QMap outputsConfig(const QList &outputs, outputHashes[output] = hash; } - QMap ret; + QHash ret; const auto outputsJson = doc.array(); for (const auto &outputJson : outputsJson) { const auto outputObject = outputJson.toObject();