Ignore my last post. Garbage. I had overlooked a rather obvious fact
of screen manufacturing: each method will have slight variance in terms
of absolute PPI, resulting in variance not only in physical pixelDensity
differences but in how accurately the OS will bother to account for them
in
Thanks, Brian. With your stats we now have our first anomaly, between
the two platforms:
The iOS math checks out in terms of the reported logical metrics
matching the physical pixels per the pixel density.
But when we compare the iPhone 5.5" screen with the LG Stylo 5.5"
screen, LiveCode
iPhone6SPlus: 5.5" 1242x2208 414x736 414x736 3
On Sat, Oct 21, 2017 at 3:54 PM, Richard Gaskin via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Yesterday, in reply to Ralph's post I included these notes about mobile
> metrics:
>
> > ...it seems that LC's resolution-independence works
Yesterday, in reply to Ralph's post I included these notes about mobile
metrics:
> ...it seems that LC's resolution-independence works very much like
> that of browsers (probably using the same OS APIs under the hood),
> using logical metrics rather than physical.
...
> I just ran a quick test
Thank you for bringing this to the list, Ralph:
> On Richards talk yesterday I brought this up and I am moving it to the
> list.
>
> Say you have 3 Android devices:
> 1) Phone sized.
> 2) Note sized.
> 3) Tablet sized.
> It is entirely possible that these 3 devices have the same(or close)
>
On Richards talk yesterday I brought this up and I am moving it to the list.
Say you have 3 Android devices:
1) Phone sized.
2) Note sized.
3) Tablet sized.
It is entirely possible that these 3 devices have the same(or close) number
x/y of pixels.
How can I determine the physical size of mobile
