On terça-feira, 17 de setembro de 2013 11:01:15, Rutledge Shawn wrote:
> On 17 Sep 2013, at 10:05 AM, noname wrote:
> > Hi everyone,
> > 
> > using Qt 5.1.1, is there a more accurate way to determine the physical
> > display size or the DPI of a mobile android device, than using
> > QScreen::physicalSize or QScreen::physicalDotsPerInch(X/Y)? Those values
> > aren't correct on most of our testing devices.
> > Example: One device has a ~218dpi display, but
> > QScreen::physicalDotsPerInch (also QScreen::physicalDotsPerInchX and
> > QScreen::physicalDotsPerInchY) returns ~160dpi.
> > QScreen::logicalDotsPerInch returns 150.
> > Then again, on some devices the correct values are reported and
> > everything works as it should.
> 
> IMO that sounds like a bug; logical can be different than physical, but
> physical resolution should be correct.  Please file a bug at
> bugreports.qt-project.org and give details about which devices have it
> correct and which don't, which SDK and NDK and API versions you are using,
> etc.

Note that the bug might be in the device itself. It's not uncommon for screens 
to lie about their physical sizes in their EDID.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to