Android splash

[EddieLee]

Hi all,

I know that for Android the splash settings on the standalone setting doesn’t work, do you guys have a workaround for this? Currently it takes a few secs for my app to load and I don’t want the user to see a black screen. So I created a cd with an image and a loading scrollbar on the first cd of the stack but it only shows after the black screen and not during. Any ideas how to lessen the time of the black screen or replace the black screen with something else?

Thanks !
Eddie

[jacque]

Make your working stack a substack of a new mainstack. The mainstack can have the progress bar and almost no code except to open the substack. The mainstack will open instantly and will be visible until the substack opens. When that happens you may want to hide the mainstack.

[AndyP]

Also I've found on Android, avoid having any code in a preOpenStack handler

[FourthWorld]

Also I've found on Android, avoid having any code in a preOpenStack handler

What did you try that didn't work out as expected?

[AndyP]

Also I've found on Android, avoid having any code in a preOpenStack handler

What did you try that didn't work out as expected?

Just in general, if I have code in the preOpenStack handler, I've noticed that the delay with the black screen on startup is longer.

[jacque]

Just in general, if I have code in the preOpenStack handler, I've noticed that the delay with the black screen on startup is longer.

Right, I see that too. That's why I move everything that isn't visual over to an openCard handler when possible. If the OP can do that, then a new mainstack may not be necessary.

[FourthWorld]

Also I've found on Android, avoid having any code in a preOpenStack handler

What did you try that didn't work out as expected?

Just in general, if I have code in the preOpenStack handler, I've noticed that the delay with the black screen on startup is longer.

That will always be the case, on all platforms, since the pre* messages execute before rendering.

It's more noticeable on mobile platforms because compute resources are more modest there.