This repository has been archived by the owner on Aug 22, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 110
QQC2 auto-scaling does not function under qtwayland #1320
Labels
Comments
UniversalSuperBox
added a commit
to ubports/morph-browser
that referenced
this issue
Aug 13, 2020
This should not be proposed into xenial as it breaks automatic rescaling when moving between displays of different pixel densities. If you would like to propose this, first find a way to diagnose that Qt auto-scaling is not working, then use this workaround based on that knowledge. Make scaling work correctly on different size displays that don't have auto-scaling by dividing the current GRID_UNIT_PX by the default (8). Works around ubports/ubuntu-touch#1320
UniversalSuperBox
added a commit
to ubports/morph-browser
that referenced
this issue
Nov 30, 2020
This should not be proposed into xenial as it breaks automatic rescaling when moving between displays of different pixel densities. If you would like to propose this, first find a way to diagnose that Qt auto-scaling is not working, then use this workaround based on that knowledge. Make scaling work correctly on different size displays that don't have auto-scaling by dividing the current GRID_UNIT_PX by the default (8). Works around ubports/ubuntu-touch#1320
UniversalSuperBox
added a commit
to ubports/morph-browser
that referenced
this issue
Nov 30, 2020
This should not be proposed into xenial as it breaks automatic rescaling when moving between displays of different pixel densities. If you would like to propose this, first find a way to diagnose that Qt auto-scaling is not working, then use this workaround based on that knowledge. Make scaling work correctly on different size displays that don't have auto-scaling by dividing the current GRID_UNIT_PX by the default (8). Works around ubports/ubuntu-touch#1320
UniversalSuperBox
added a commit
to ubports/morph-browser
that referenced
this issue
Nov 30, 2020
This should not be proposed into xenial as it breaks automatic rescaling when moving between displays of different pixel densities. If you would like to propose this, first find a way to diagnose that Qt auto-scaling is not working, then use this workaround based on that knowledge. Make scaling work correctly on different size displays that don't have auto-scaling by dividing the current GRID_UNIT_PX by the default (8). Works around ubports/ubuntu-touch#1320
mariogrip
pushed a commit
to ubports/morph-browser
that referenced
this issue
Jan 26, 2021
This should not be proposed into xenial as it breaks automatic rescaling when moving between displays of different pixel densities. If you would like to propose this, first find a way to diagnose that Qt auto-scaling is not working, then use this workaround based on that knowledge. Make scaling work correctly on different size displays that don't have auto-scaling by dividing the current GRID_UNIT_PX by the default (8). Works around ubports/ubuntu-touch#1320
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Let's repeat #841 again, but this time for Wayland! Yaaaaay!
The Qt autoscaling doesn't work under QtWayland on Ubuntu Touch, instead returning
1
for any sized screen. Instead, thepixelDensity()
function of the QtScreen should return a number based on how large the screen is. This causes Kirigami and similar apps to not scale at all.This was fixed in QtUbuntu with ubports/qtubuntu#5. It's possible that QtMir is not passing a required value to QtWayland.
The text was updated successfully, but these errors were encountered: