The only time I've seen Capabilities.screenDPI report an unexpected value was because the mobile device manufacturer actually chose the incorrect value on purpose. It was a tablet and they wanted to scale apps to phone resolution, for some reason. Once I knew that, the unexpected behavior I was seeing made complete sense.
I've been using Capabilities.screenDPI for years, and I think you should too because it actually works well. The reports of it being unreliable are... unreliable. At least that's been my experience, and I've been building AIR mobile apps since the beginning. - Josh On Mar 4, 2017 10:15 PM, "bilbosax" <[email protected]> wrote: My application is out of proof-of-concept and I am going to be writing the final version. I want everything to be on point right out of the gate, and I need it to work on all devices reliably. Laying out my components and scaling them correctly will be key, and this all depends on screen DPI, but unforunately, Capabilities.screenDPI is not a reliable way to get the correct DPI. Does anyone know of an ANE that fairly reliably reports the correct DPI? I have looked around, and remember reading about one somewhere, but I have been unable to find one. Thanks -- View this message in context: http://apache-flex-users. 2333346.n4.nabble.com/Screen-DPI-ANE-tp14761.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
