Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.12.11, 5.15.5, 6.1.3
-
MSVC2019
-
-
dedb29cf23959741593b2fa1481f210cd663cafb (qt/qtbase/dev) 47ba0a465e93946df3ad6f0f39fe15a4da683b0d (qt/qtbase/6.2)
Description
This is a regression bug that happened between 5.12.4 (correct) and 5.12.5 (wrong)
In the following configuration, everything works fine when creating a QAxWidget on a main display. However, when you move the app window to the secondary
screen and then create the QAxWidget, it does not render at all.
SetProcessDPIAware(); //make System-DPI Aware
QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
QCoreApplication::setAttribute(Qt::AA_UseHighDpiPixmaps);
QCoreApplication::setAttribute(Qt::AA_DontCreateNativeWidgetSiblings);
How to reproduce
0. You need two displays and one should be 150% scaling for the Qt High DPI scaling to kick in.
1. Use Qtbug96114.zip
2. Press "create Ax Widget" button in the main display -> Qt Ax widget is created and WMP is shown
3. Move the window to the second display
4. Press "create Ax Widget" button
Expected result : Qt Ax widget is rendered
Actual result : Qt Ax widget is not rendered
Attachments
Issue Links
- relates to
-
QTBUG-102982 QMenu appears at the wrong position without Per-Monitor DPI awareness
- Closed
For Gerrit Dashboard: QTBUG-96114 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
376802,6 | Fix high DPI position of foreign child windows on Windows | dev | qt/qtbase | Status: MERGED | +2 | 0 |
376952,2 | Fix high DPI position of foreign child windows on Windows | 6.2 | qt/qtbase | Status: MERGED | +2 | 0 |
377089,2 | Fix high DPI position of foreign child windows on Windows | tqtc/lts-5.15 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |