Did you remember to set your splash screen activity to not be in the history? On Jan 11, 2012 10:21 PM, "devbuzz" <[email protected]> wrote:
> I've run into an issue implementing my splash screen. I used the > SplashActivity example and everything works the first time I run my app. > > Since my application launches a service to retrieve data in the background > I > don't want multiple instances of the app running. If you are running the > app, press home and then click the icon to launch the application I expect > a > currently running instance to be activated. But this is not happening - I > get a new instance of the SplashScreen. > > I think this is happening because the SplashActivity is designated as the > mainlauncher and not my main home screen (as per the SplashActivity demo). > Also I don't want to leave the SplashScreen in memory - I call Finish() on > the SplashScreen once my main home screen is loaded so that you don't see > the SplashScreen when you hit the back button (perhaps this is part of the > problem ?) > > So my question is how do I architect this so: > a) my app starts with a SplashScreen > b) the SplashScreen shows a login screen which if successful shows > c) my main home screen > d) and then if you navigate away and then click the icon to launch my app I > want it to not show the SplashScreen but rather go directly to the running > instance of my main home screen. > > TIA > > -- > View this message in context: > http://mono-for-android.1047100.n5.nabble.com/SplashActivity-and-single-instance-tp5138098p5138098.html > Sent from the Mono for Android mailing list archive at Nabble.com. > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid >
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
