Question About Resolution Independence
colinholgate at gmail.com
Mon Feb 8 15:00:23 CET 2016
The dictionary says what the two properties are for, but they are slightly confusing. I would start by trying iphoneUseDeviceResolution true.
I think that exactFit will be the least used full screen mode. It would distort your card to match the ratio of the device. Your choices are to either not set the full screen mode, and use code to lay out all of your UI, or use noBorder or showAll, and have extra content that fills in the parts that are revealed on wider or taller devices.
Read through the topic "one-rect-for-all alpha” for a lot more discussion about that.
> On Feb 8, 2016, at 4:53 AM, Rolf Kocherhans <rolf.kocherhans at id.uzh.ch> wrote:
> Sorry that was a typo just on the eMail !
> The stack has a size of 1024*768 pixels.
> @ Richmond this size is suggested on a movie about Resolution Independence:
> I think that that Colin could be correct with his suggestion of using:
> iphoneUseDeviceResolution but there are so many possibilities (4), and I do not
> fully understand all the text in the Dictionary
> iphoneUseDeviceResolution true
> iphoneUseDeviceResolution true, true
> iphoneUseDeviceResolution true, false
> iphoneUseDeviceResolution false
> Has anyone used this already ?
> I thought that I can just use:
> on preOpenStack
> set the fullScreenMode of this stack to "exactFit"
> end preOpenStack
> And all my resolution problems would be done ?!
> What do you all use - can we really program for one screen size and deploy
> to all devices ?
>> Am 08.02.2016 um 03:48 schrieb use-livecode-request at lists.runrev.com:
>> Out of curiosity, if that's not a typo:
>>> my stack has a size of 1025*768
>> Is it the same if you use 1024*768 (exactly 4:3)?
> 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