My x3 splash is already smaller than the largest real requirement for an 
iPhone, 1242 x 2688. Mine is only 2048 x 2732. So you could argue that my x3 
splash should be even larger than I’ve supplied.

I don’t see why the system doesn’t pick the smallest size that will fit - so 
for my iPhone XS for example, which needs 1125x2436 for an exact fit, I have 
supplied my x2 splash at exactly the right size. 

I realise this is not desperately important, especially as I can adopt Andrew’s 
solution below, but there does seem to be something wrong here. It will be 
interesting to read the LC lesson on this when it comes out!

Graham

> On 22 May 2020, at 18:41, Andrew at MidWest Coast Media via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> I had the same problem when creating storyboards: the icon was too big. My 
> app was portrait so I could tell the dimensions were backwards, but when 
> using the the recommended sizes the logo ran off the edges. Placing the 1x 
> version in the 2x slot (and the 2x in the 3x slot) seemed to make things look 
> more like what I expected.
> 
> Making the first card of the stack have the same background color as the 
> Storyboard worked fine, then just...
> unlock screen for visual effect
> go next card
> unlock screen with visual effect “dissolve” very fast
> 
> —Andrew Bell


> On 22 May 2020, at 14:48, panagiotis merakos via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> *>>>>>LC 9.6.0 rc1 reported that I hadn’t provided a portrait splash screen
> for iPad*
> 
> Yes, this is a bug in LC 9.6 RC-1, which is fixed in LC 9.6 RC-2.
> 
> *>>>>>and the Simulator showed the splash screen too large for the screen
> of the device *
> 
> Hmm, then I would expect the splash to show too large in the physical
> device as well. In this case, I would try with a smaller splash.
> 
> Kind regards,
> Panos
> --
> 
> On Fri, 22 May 2020 at 15:25, Graham Samuel via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>> I did that, so fine, but noticed two issues: when making the standalone LC
>> 9.6.0 rc1 reported that I hadn’t provided a portrait splash screen for
>> iPad, when in fact there is no way of doing so since the storyboard change;
>> and the Simulator showed the splash screen too large for the screen of the
>> device (an iPhone XS). (Not sure if the real app does that as I’m having
>> trouble uploading - that’s a different conversation.)
>> 
>> Graham
>> 
>>> On 22 May 2020, at 13:51, panagiotis merakos via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>> 
>>> Just realised that the image sizes I suggested are for landscape, so if
>>> your app uses portrait, just swap the width with the height.
>>> 
>>> 
>>> 
>>> On Sun, 17 May 2020 at 21:35, Colin Holgate via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
>>>> What I’ve done for a while is to use a flat color that is the average of
>>>> the colors in the actual title screen. The splash screen is not around
>> for
>>>> very long, and with there being lots of different sizes required, a
>>>> detailed splash screen could possibly take up 50 MB of app side, for the
>>>> sake of a fraction of a second.
>>>> 
>>>> In the best case it feels like the title screen faded into view. In
>> fact,
>>>> you could do that, quickly fade in from a matching flat background
>> color.
>>>> 
>>>> 
>>>>> On May 17, 2020, at 10:58 AM, panagiotis merakos via use-livecode <
>>>> use-livecode@lists.runrev.com> wrote:
>>>>> 
>>>>> Hello Graham,
>>>>> 
>>>>> The new storyboard mechanism has some restrictions as it is (we might
>>>>> enhance it in the future)
>>>>> 
>>>>> For example it is no longer possible to have an exact (pixel) matching
>> of
>>>>> the splash screen and the first card of the stack as it appears on the
>>>>> device
>>>>> 
>>>>> So the best suggestion now is to use a splash image that has just a
>> logo
>>>> at
>>>>> the center and it is transparent, and also to set the background of the
>>>>> splash in the standalone settings.
>>>>> 
>>>>> In that way, in all devices (ipads/iphones) you will get a centered
>> logo
>>>>> with the background you set in the standalone settings (or you can
>> choose
>>>>> to not set the background - in this case the default background color
>>>> will
>>>>> be used depending on the device appearance: white if the device is on
>>>> light
>>>>> mode and black if the device is on dark mode)
>>>>> 
>>>>> Of course, if you do not wish to have a splash that shows just a logo,
>>>> you
>>>>> can choose a regular image (or 3 regular images, one for each 1x,2x,3x
>>>>> slots) and also set the background color to match the image background
>>>>> color. In this case, depending of the device, the app will use the one
>> of
>>>>> the three images that is closer to the device screen size, and will
>>>> center
>>>>> this image to the screen.
>>>>> 
>>>>> This means that the image in some devices will either match exactly, or
>>>> it
>>>>> will be larger (in this case it will be cropped and the edges will not
>>>>> show), or it will be smaller (in this case it will be centered at the
>>>>> device screen, and the left/top/right/bottom areas will show the
>>>> background
>>>>> color that was set in the standalone settings.
>>>>> 
>>>>> One might ask, what size should the images be then? Well, it depends on
>>>> the
>>>>> images (i.e. how much content they have at the center, and if you are
>> OK
>>>> if
>>>>> some of the content at the edges is cropped etc). A rule of thumb - as
>> I
>>>>> understand it - is the following:
>>>>> 
>>>>> -use a "small", a "medium" and a "large" image for each of the 1x, 2x
>> and
>>>>> 3x slots, where "small" is the smallest image you used before the
>>>>> storyboard, "large" is the largest you used before, and "medium" is
>>>>> something in-between.
>>>>> 
>>>>> For example, you could try images with these dimensions:
>>>>> 
>>>>> - 1334x750
>>>>> - 2208x1242 (x2)
>>>>> - 2732x2048 (x3)
>>>>> 
>>>>> Hope this helps.
>>>>> 
>>>>> We will write a lesson for this topic soon.
>>>>> 
>>>>> Kind regards,
>>>>> Panos
>>>>> --
>>>>> 
>>>>> On Sat, 16 May 2020 at 17:49, Graham Samuel via use-livecode <
>>>>> use-livecode@lists.runrev.com> wrote:
>>>>> 
>>>>>> This is not to answer my own question, but to emphasise the apparent
>>>>>> difficulty of getting this aspect of creating an iOS app right just by
>>>>>> using just LC and a reasonable graphics editor on a Mac. It means to
>> me
>>>>>> that a lot of careful instructions need to be provided by somebody in
>>>> the
>>>>>> LC universe, since the policy (I sincerely hope!) is to get LC
>>>> developers
>>>>>> to avoid getting deep into XCode. I found this, which frankly scares
>> me.
>>>>>> 
>>>>>> https://wiki.starling-framework.org/manual/ios_launch_images
>>>>>> 
>>>>>> Can anyone help me to a less nerdy way of getting this right? I don’t
>>>>>> even know what a storyboard is!
>>>>>> 
>>>>>> Graham
>>>>>> 
>>>>>>> On 16 May 2020, at 00:40, Graham Samuel via use-livecode <
>>>>>> use-livecode@lists.runrev.com> wrote:
>>>>>>> 
>>>>>>> I see that the iOS Standalone Settings have changed in this version,
>> no
>>>>>> doubt to accommodate Apple’s new rules. One is required to provide six
>>>>>> images as “Launch Images” under the “Splash” tab. It seems that
>> there’s
>>>> an
>>>>>> image, a 2x image and a 3x image, and then another three for dark
>> mode.
>>>>>>> 
>>>>>>> There is no tooltip to suggest how large these images should be - in
>>>>>> previous versions they had to be tailored to different device screen
>>>> sizes.
>>>>>> Now it seems anything goes, or does it?
>>>>>>> 
>>>>>>> Can anyone explain what the dimensions of these images are supposed
>> to
>>>>>> be? Does “2x” just mean twice the original size in each direction or
>>>> what?
>>>>>> Can’t see anything in the release notes, but maybe I wasn’t paying
>>>>>> attention.
>>>>>>> 
>>>>>>> Graham
>>>>>>> _______________________________________________
>>>>>>> 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
>>>>>> 
>>>>> _______________________________________________
>>>>> 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
>>>> 
>>> _______________________________________________
>>> 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
>> 
> _______________________________________________
> 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