Splash screen display logic is complicated and uses flag in nonvolatile memory - should be simplified

[GoogleCodeExporter]

The splash screen should be displayed only when the user launches the 
application for the first time.  If the game loses focus due to the home button 
being pressed or some other application taking over, when the game regains 
focus the splash screen should not be displayed.

If the user presses the back button, the splash screen should be displayed the 
next time the application is launched.

Note that this is actually already implemented, but is accomplished via using a 
flag that is located in the shared preferences, and the logic is overly 
complicated.

A simple check of whether the game activity is already running when the splash 
screen activity starts should work, but I am currently unaware of how to do 
this.

The splash screen activity currently creates an intent to start the game.  If 
the splash screen activity were started by the game, then this would be a 
non-issue.

Original issue reported on code.google.com by forter...@gmail.com on 22 Mar 2013 at 11:21

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I just found out a quirk of the intent filters in the AndroidManifest.xml - if 
more than one action or category filter are used, they don't work correctly, 
and the action must be MAIN and the category LAUNCHER in order for the debugger 
to launch the application correctly if it is set to use the default activity.

Original comment by forter...@gmail.com on 23 Mar 2013 at 1:24

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by forter...@gmail.com on 20 Apr 2013 at 3:35

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Verified in version 1.18.

Original comment by forter...@gmail.com on 8 Jul 2013 at 1:52

• Changed state: Verified