how to properly use the fullscreenmode and screen scaling

[J. Landman Gay]

Typically you need to handle field placement yourself in script, moving 
the controls up on keyboardActivated and back down on 
keyboardDeactivated. However, there's an unintentional side-effect when 
setting acceleratedRendering to true in a stack; when the keyboard shows 
up, the whole card scrolls up by the height of the keyboard. I haven't 
found this useful very often, since it frequently scrolls the field I 
want to target right off the top of the screen. But if your layout 
accomodates that behavior it may be useful.

The "showAll" fullscreenMode ensures that the full height of the stack 
contents are visible on screen. This means on narrower screens, 
left/right edges may be cropped and on wider screens there may be an 
extra margin.

The "noBorder" mode ensures that the full width of the content is 
visible, which means in portrait mode you'll get a tiny little stack 
that fits horizontally within the width of the device, and large empty 
areas at top and bottom.

To allow both orientations, you can use the orientationChanged message 
to set the fullscreenMode to either showAll or noBorder, depending on 
which way the device is turning. Or you can write scripts that resize 
and place all card controls depending on the layout you want.

On 10/27/18 4:40 PM, Mike for GDC via use-livecode wrote
> When I deploy it to my 8 inch Samsung Tab A (Android)  it is ok in the
> Landscape mode, with one exception.  When I go to enter data, the keyboard
> covers up some of the screen that I need to enter data.  It does not scroll
> up to let me get
> 
> to the field of entry.  When it is in Portrait mode I can usually see the
> field but the stack only takes up about half the screen so it is very small.
> When I deploy it on the Samsung S8, it is even worse in that the entire
> screen is not used and therefore
> 
> it is way too small to really use it.  I would hope there is a way to take
> advantage of all the screen space so as the used has a larger screen to view
> and enter data.    It seems the keyboard is the same size and not scaled at
> all.
> 
>   
> 
> Here are the script statements that I put in my "preopenstack" of my first
> card:
> 
>   
> 
> set the fullscreenMode of this stack to "showAll"
> 
> put "portrait,portrait upside down,landscape left,landscape right" into
> theallowed
> 
> -- Function Call
> 
> mobileSetAllowedOrientations theallowed
> 
>   
> 
> I have also used the "exactfit", "noborder" and "soScale" options but they
> 
> any help with suggestions or example code of how it should work would be
> greatly appreciated.
> 
> Thanks.
> 
> Mike
> 
>   
> 
>   
> 
>   
> 
> _______________________________________________
> 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
> 


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com