‚ÄčOk. Took Jacque's advice‚Äč, and my stack's working screenRect is
0,24,360,592.

Now I'm unsure whether my stack's size is 360 x 592, or (width = item 3 -
item) x (height = item 4 -item 2).

Thanks.

--
Nicolas Cueto



On 2 February 2018 at 17:53, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 1/31/18 5:23 PM, Nicolas Cueto via use-livecode wrote:
>
>> 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?
>>
>
> Probably the area occupied by the status bar is pushing the stack down.
> Get "the working screenrect" to find out the actual screen dimensions your
> stack can use.
>
> Since every Android device is different, it's usually easier to set the
> fullscreenMode to "showAll" and let the LC engine adjust the size.
>
>
> --
> Jacqueline Landman Gay         |     jac...@hyperactivesw.com
> HyperActive Software           |     http://www.hyperactivesw.com
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to