One Rect For All specificaiton
prothero at earthednet.org
Mon Jan 4 14:55:06 EST 2016
Colin and Brahmanathaswami:
When this discussion topic is finally resolved, it would be wonderful and extremely useful if a summaryof the best practice, with comments on implementation consequences, was posted somewhere. This is an important issue and will save the rest of us who haven’t faced this issue yet, a lot of time.
> On Jan 4, 2016, at 5:15 AM, Colin Holgate <colinholgate at gmail.com> wrote:
> With showAll you are guaranteed to see all of the original card contents. On a wider screen the height of the card is still fitted into the height of the device, and the extra width is filled in with the content that was off the edges of the card.
> I’ve used showAll for books, where I wanted to be sure to not lose any of the height, and games, where I wanted to be sure not to lose any of the width. For one game though it was better to do the noBorder compromise, so that it wasn’t geared towards either wider or not so wide devices. Suggesting noBorder for you was after asking questions about whether you could work in the same way.
>> On Jan 3, 2016, at 11:18 PM, Sannyasin Brahmanathaswami <brahma at hindu.org> wrote:
>> Colin wrote: "You could use the 1024x768 iPad preset and then have extra content that extends out to 171 pixels either side of the card, that you don’t normally se while working on the stack.”
>> But then wouldn’t you have the issue of losing the top and bottom if you run the same app in iPhone 6+ landscape?
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode