[Interest] A bug in Qt 5.3.1 for Android?
Alexander Zakharov
alexander.v.zakharov at gmail.com
Tue Jul 1 09:33:11 CEST 2014
> My testing result:
>
> Qt 5.3.0 + Nexus 5 (4.4.2)
> primaryScreen()->physicalDotsPerInch() 443.934
> Qt 5.3.0 + Samsung Galaxy Note 2
> primaryScreen()->physicalDotsPerInch() 264.903
>
> Qt 5.3.1 + Nexus 5 (4.4.2)
> primaryScreen()->physicalDotsPerInch() 453.754
> Qt 5.3.1 + Samsung Galaxy Note 2
> primaryScreen()->physicalDotsPerInch() 270.284
>
> Although it don't return infinity , Qt 5.3.1 produces value different
> than 5.3.0
Thanks, your results pushed my thoughts in a right direction. In my
program physicalDotsPerInch() is called from the main window's
constructor and it is this call that stopped working. Calling
physicalDotsPerInch() later, when the main window is shown, produces a
value of 151.588, which is (almost) correct (I do not remember the exact
DPI produced by 5.3.0, but it was close).
> btw , I got another issue after upgraded to Qt 5.3.1 on Android.. Seem
> that there has some large changes from 5.3.0 to 5.3.1
> [#QTBUG-39977] Full screen mode do not work correctly on Nexus 5 v4.4.2
> - Qt Bug Tracker
> <https://bugreports.qt-project.org/browse/QTBUG-39977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-249119>
I do not use full screen mode in my application (the main window is
always maximized), so I did not test it in 5.3.0 and earlier versions.
However, now, when I change showMaximized() call to showFullScreen() in
the main window's constructor, the bottom bar does not disappear, but
stays on screen, partially hiding the window, as shown in Step 3
screenshot of the described bug.
More information about the Interest
mailing list