diff options
| author | Laszlo Agocs <[email protected]> | 2023-09-21 14:03:47 +0200 |
|---|---|---|
| committer | Laszlo Agocs <[email protected]> | 2023-09-25 15:12:05 +0200 |
| commit | 9cad3fcc971f50ad7e53a7be3746d751639976b5 (patch) | |
| tree | e6efd0cf6af8ce3f55c6dbc23fc5ad3db7304714 | |
| parent | 8a5a5f6c9773dc41b4c8685bc1c6bd34ce49a320 (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
Pick-to: 6.6
Reviewed-by: Christian Strømme <[email protected]>
| -rw-r--r-- | src/platformsupport/kmsconvenience/qkmsdevice.cpp | 1 |
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) |