aboutsummaryrefslogtreecommitdiff
path: root/python
diff options
context:
space:
mode:
authorWeifeng Liu <weifeng.liu.z@gmail.com>2025-05-11 15:33:17 +0800
committerMarc-André Lureau <marcandre.lureau@redhat.com>2025-05-24 17:03:50 +0200
commita1b28f71f7ff0fcafbe0672b788e8e57ee4fe8f6 (patch)
tree56c0f2c3fe1eb6df3596c4bc545c558e5a1fe802 /python
parent02f25490879096b679ab3d7cb7f0facfef7c6484 (diff)
downloadqemu-a1b28f71f7ff0fcafbe0672b788e8e57ee4fe8f6.zip
qemu-a1b28f71f7ff0fcafbe0672b788e8e57ee4fe8f6.tar.gz
qemu-a1b28f71f7ff0fcafbe0672b788e8e57ee4fe8f6.tar.bz2
ui/gtk: Consider scaling when propagating ui info
The ui width and height sent to guest is supposed to be in buffer coordinate. Hence conversion is required. If scaling (global window scale and zooming scale) is not respected in non-free-scale mode, window size could keep changing because of the existence of the iteration of the following steps: 1. In resize event or configure event, a size larger (or smaller) than the currently used one might be calculated due to not considering scaling. 2. On reception of the display size change event in guest, the guest might decide to do a mode setting and use the larger (or smaller) mode. 3. When the new guest scan-out command arrives, QEMU would request the window size to change to fit the new buffer size. This will trigger a resize event or a configure event, making us go back to step 1. Signed-off-by: Weifeng Liu <weifeng.liu.z@gmail.com> Message-ID: <20250511073337.876650-8-weifeng.liu.z@gmail.com> Acked-by: Gerd Hoffmann <kraxel@redhat.com> Acked-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions