-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
Initial work on the new fast splash screen #186
Conversation
Small tip: granted, this will never be as fast as the UWP splash screen, but should be able to at least improve this a tiny bit more if you disable the XAML generated splash screen, and show your custom splash screen before anything else. That is, before even loading any WinAppSDK/WinUI bit of code, creating the |
@Sergio0694 it does make a little difference. Not a whole lot though. But for completeness sake, I updated the functional test app to show both ways |
Yeah, that's the best we can do from here. The ideal way would be to just do what UWP does, where the OS shows the splash screen and the window before any of the app even runs, but of course that requires OS support and isn't an option 😅 |
It's still pretty responsive with a sub-second launch time on my machine. Well before you start thinking "did I click it"? |
Yup, I mean I haven't seen this in action but I believe it looks completely acceptable. Was just saying that sadly there's only so much you can do without OS support. The UWP splash screen has a bunch of advantages like:
That said, that was just me thinking out loud, and I'm sure this custom splash screen will already be useful to folks looking for something like this. Great job! 🙂 |
Fixes #87
Usage:
In MainWindow when your window has loaded, call
MyApp.Splash.Hide();
(with optional timespan parameter to fade out)There's also an option to just specify an image path and not rely on app manifest (unpackaged apps would need that):
SimpleSplashScreen.ShowSplashScreenImage(full_path_to_image);