https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13877
--- Comment #17 from Gerald Combs <ger...@wireshark.org> ---
I was able to cobble together a HiDPI Windows system and run some tests.
Physcial setup: Lenovo T430 with the following displays:
Built in: 1600 x 900, 100% scaling
External: (3480 x 2160), 150% scaling
Wireshark build information:
----
Version 2.5.0 (v2.5.0rc0-535-g0b6ecd0121)
Copyright 1998-2017 Gerald Combs <ger...@wireshark.org> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with Qt 5.9.1, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.11, with SMI 0.4.8, with c-ares 1.13.0, with Lua 5.2.4, with GnuTLS
3.4.11, with Gcrypt 1.7.6, with MIT Kerberos, with GeoIP, with nghttp2 1.14.0,
with LZ4, with Snappy, with libxml2 2.9.4, with QtMultimedia, with AirPcap,
with
SBC, with SpanDSP.
Running on 64-bit Windows 10, build 15063, with Intel(R) Core(TM)
i5-3320M CPU @ 2.60GHz (with SSE4.2), with 8011 MB of physical memory, with
locale English_United States.1252, with WinPcap version 4.1.3 (packet.dll
version 4.1.0.2980), based on libpcap version 1.0 branch 1_0_rel0b (20091008),
with GnuTLS 3.4.11, with Gcrypt 1.7.6, with AirPcap 4.1.0 build 1622.
Built using Microsoft Visual C++ 14.0 build 24215
---
The observations below were made after doing the following:
- Adding GeometryStateDialog::event, which printed information about the device
pixel ratio, DPI, and font height and compiling Wireshark.
- Setting or unsetting QT_AUTO_SCREEN_SCALE_FACTOR as noted below.
- Running Wireshark
- Dragging the main window and preferences dialog between screens.
Test 1. Running `set QT_AUTO_SCREEN_SCALE_FACTOR=0`, then running Wireshark:
Notable events when moving a window between displays:
Move, ScreenChangeInternal, FontChanged, LayoutRequest, Resize
4K display behavior:
- devicePixelRatio and devicePixelRatioF are 1. physicalDpiX is 163.
logicalDpiX is 144. fontMetrics height is 21.
- Geometries are halved? Windows are small and shifted up and to the left.
QTBUG-55510?
- Toolbar and other icons are tiny.
- Some layout items (e.g. line edits in Prefs -> Statistics) are too short.
- Menus are too small when opening them the first time, then fine subsequent
times. QTBUG-59794.
- Application text (e.g. menu titles) is the same size as the desktop context
menu.
Built in display behavior:
- devicePixelRatio and devicePixelRatioF are 1. physicalDpiX is 131.
logicalDpiX is 96. fontMetrics height is 13.
- Everything seems to behave normally.
Test 2. Running `set QT_AUTO_SCREEN_SCALE_FACTOR=1`, then running Wireshark:
Notable events when moving a window between displays:
Move, ScreenChangeInternal, Resize
4K display issues:
- devicePixelRatio and devicePixelRatioF are 2. physicalDpiX is 81!?
LlogicalDpiXis 96. fontMetrics height is 13.
- Main welcome interface scroll bar is half width.
- Toolbar and other icons are normal.
- Application text (e.g. menu titles) is slightly larger than the desktop
context menu, probably due to the issues described in QTBUG-53022.
Built in display issues:
- devicePixelRatio and devicePixelRatioF are 1. physicalDpiX is 131.
logicalDpiX is 96. fontMetrics height is 13.
- Main welcome interface scroll bar is half width.
- Windows moved from the 4K display are huge. QTBUG-55510?
- Everything else is normal.
I also tried setting the 4K scaling factor to 200% and
QT_AUTO_SCREEN_SCALE_FACTOR=1. The application text was the same size as the
desktop context menu, which is consistent with QTBUG-53022.
I think our best bet is to set Qt::AA_EnableHighDpiScaling at startup (which is
the same as setting QT_AUTO_SCREEN_SCALE_FACTOR=1) and fix any remaining UI
issues we find.
--
You are receiving this mail because:
You are watching all bug changes.
___________________________________________________________________________
Sent via: Wireshark-bugs mailing list <wireshark-bugs@wireshark.org>
Archives: https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe
