discrepancy between official device metric and LC stack size

[Ralph DiMola]

Nicolas,

Does that device have "old hardware keys" soft buttons on the bottom? On
some devices this is shown if the manifest does not include some key that
says your app no longer needs the "old hardware keys". Android has been
phasing the hardware keys out. Setting this key in the manifests not an
option on the Android standalone setting. Looking at my code I see I use
"the rect of this card" to account for the soft keys but not the keyboard.
To account for the keyboard and soft "old hardware keys":

put 0 into tLeft

put 0 into tTop

put item 3 of the effective working screenrect - item 1 of the effective
working screenrect into tRight

put item 4 of the effective working screenrect - item 2 of the effective
working screenrect into tBottom

This has been working for me on both iOS and Android.

Ralph DiMola
IT Director
Evergreen Information Services
rdimola at evergreeninfo.net

-----Original Message-----
From: use-livecode [mailto:use-livecode-bounces at lists.runrev.com] On Behalf
Of Nicolas Cueto via use-livecode
Sent: Wednesday, January 31, 2018 6:24 PM
To: How to use LiveCode
Cc: Nicolas Cueto
Subject: discrepancy between official device metric and LC stack size

I test my mobile stacks on a Nexus 5, and, in portrait orientation, many
bottom pixels are offscreen, even though for width and height I follow
exactly the numbers given in dp at the website Device Metrics
<https://material.io/devices/> .

Why is it cut off? And how can I avoid this? Is there an LC keyword, like
"effective" or "working", that I should be including.... if so, how?

Thanks.

--
Nicolas Cueto
_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode