-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splash Screen on startup #19
Comments
What I like about Flex mobile SplashScreen is the "zoom" scale mode. That allows to use a single .png file that will look good enough in most screens and aspect ratios. If you need help with this feature I can do some testing to see how different scale modes look. |
Hi Josh, did you make any progress on the splash screen implementation? thanks, |
@quick6black No, I haven't done any work on this one yet. |
this would be awesome 👍 |
(edited: Don't use this!!! See the corrected solution below in the answers...) I extended the StarlingBootstrap so that I could have my own splashscreen (bitmap) created without any flickering after the default iOS splash image. I also considered the "zoom" to put the image on the correct place. Since I passed through here when I was looking for a solution, maybe this can help someone else out there: :)
I'm saving a reference to the Bitmap on a Global static variable (ugly, I know) so I can fade it out and then dispose it when I'm done loading and preparing everything. The main reason for me is the flicker time between the iOS splash goes away and the context3d is created. If it's too dumb of me I'd like to know also! Wish you all the best! |
Ok, it only worked on debug and "Fast" mode. When publishing on iOS with "Standard" mode the app crashes. @joshtynjala , could you help me solving this, please? What am I missing to extend the StarlingBootstrap? Help, pls? |
I don't see anything wrong with your code. It's probably a bug in the iOS packaging. Sometimes when it optimizes more, these issues pop up, and you can tweak your code a bit to compensate. The first thing I would try is moving your code in the constructor after the super() call. I could see that potentially being the place where the packaging has an issue. Next, I would try temporarily remove the code in the constructor to see if your custom bootstrap works simply with your info() override. Then, I'd try removing only some parts of the constructor code. Basically, you're trying to narrow down exactly what is causing the crash. Once it stops crashing, you can add smaller parts back in until it crashes again. That'll help you figure out exactly which line it is, and you can try tweaking things to work around the issue. |
@joshtynjala, Thanks very very much for the answer...it lead me to a good path and I found the problem. Accessing the static variable from the Globals class where I was storing my splash was causing the crash. Wasn't immediate, though....but after loading the theme the app crashed... So, for everyone who needs this...I've stored the reference on the bootstrap class itself and all worked...no flickering anymore and my client is happy now:
Enjoy it! :) (And thanks again, Josh, for the awesome platform!) |
StarlingBootstrap should be able to display a splash screen until Starling is initialized and the application is created. Maybe with a minimum time.
Random notes and ideas:
Here's how Flex does it:
Adobe Flex 4.6: Define a mobile application and a splash screen
The text was updated successfully, but these errors were encountered: