summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLaszlo Agocs <[email protected]>2023-09-21 14:03:47 +0200
committerQt Cherry-pick Bot <[email protected]>2023-09-26 16:37:35 +0000
commit730959d6cec8ceadc8766b08977fb3bf66950ba4 (patch)
tree6adaa8c0089c0a13bd7c203197d23843a08d46b7
parent0d7f2dfa1c4c0bae82643cd3cc90b1439f81b490 (diff)
kms: Print the screen virtual position in the logs
It is impossible to see otherwise what is going on. What's worse, it prints the screen geometry (that does not include the virtual desktop adjustment), which is incredibly confusing. Change-Id: Ie67a4d8110a0b5c9cb75e6290f06c857a980d2c8 Reviewed-by: Christian Strømme <[email protected]> (cherry picked from commit 9cad3fcc971f50ad7e53a7be3746d751639976b5) Reviewed-by: Qt Cherry-pick Bot <[email protected]>
-rw-r--r--src/platformsupport/kmsconvenience/qkmsdevice.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/platformsupport/kmsconvenience/qkmsdevice.cpp b/src/platformsupport/kmsconvenience/qkmsdevice.cpp
index 89b6df605b8..421e9f05c02 100644
--- a/src/platformsupport/kmsconvenience/qkmsdevice.cpp
+++ b/src/platformsupport/kmsconvenience/qkmsdevice.cpp
@@ -716,6 +716,7 @@ void QKmsDevice::createScreens()
// virtualIndex. This is not only handy but also required since for instance
// evdevtouch relies on it when performing touch device - screen mapping.
if (!m_screenConfig->separateScreens()) {
+ qCDebug(qLcKmsDebug) << " virtual position is" << virtualPos;
siblings.append(s);
virtualPositions.append(virtualPos);
if (orderedScreen.vinfo.isPrimary)