iOS scrollers

[andrew at midwestcoastmedia.com]

I can confirm this issue and have made a sample stack documenting it  
(but can't find the bug report @ quality.livecode.com to update).

Here are the results of my testing of the data grid scroller with the  
various fullscreenMode options...
set the fullscreenMode of me to "showAll" // CUTS OFF LAST ITEM
set the fullscreenMode of me to "noBorder" // WORKS
set the fullscreenMode of me to "letterbox" // CUTS OFF LAST ITEM
set the fullscreenMode of me to "exactFit" // WORKS
set the fullscreenMode of me to "noScale" // CUTS OFF LAST ~2.5 ITEMS
set the fullscreenMode of me to EMPTY // WORKS

You can download my sample stack from:
https colon slash slash
iu dot box dot com
slash s slash
sj3lca0gxcor4415f96te8stny5kqws9


--Andrew Bell


> From: Sannyasin Brahmanathaswami <brahma at hindu.org>
> Subject: Re: iOS scrollers
>
> Perhaps I misunderstand you, but IMHO, "it not rocket science"
>
> Regardless of the device or fullscreenmode. I use (and I think  
> jacque uses) the card rect?
>
> If  we set a scroller to the "formatterHeight", in any model or  
> "mode" context, the user should be able to scroll right to the  
> bottom, and see, its contents -- in this case a field.
>
> It a confirmed bug, but it hasn't been solved/merged yet.
>
>
> It would be good to have a simple stack to test that only is for  
> showing the problem. One thing I would look at is how you are  
> measuring coordinates when using ShowAll. With ShowAll and Portrait,  
> of a card that is iPhone 4 sized, zero Y is not at the top of the  
> iPhone 5 screen. If you are finding a way to base things off of the  
> visible top of the screen, and not using the top of the card, then  
> things will go wrong.