anchor.diff:  a|Call this method to start a jME3 game. By default this opens a new jME3 window, initializes the scene, and starts the event loop.
   
   a|restart()
  -a|Loads modified <<jme3/intermediate/appsettings#,AppSettings>> into the current application context.
  +a|Loads modified xref:jme3/intermediate/appsettings.adoc[AppSettings] into the current application context.
   
   a|stop()
   a|Stops the running jME3 game and closes the jME3 window.
  
positive.code: 
  [TIP]
  ====
  Use `app.setShowSettings(true);` to present the user with a splashscreen and the built-in display settings dialog when starting the game; or use `app.setShowSettings(false);` to hide the built-in screen (in this case, you may want to provide a custom splashscreen and settings panel). Set this boolean before calling `app.start()` in the `main()` method of the SimpleApplication. See also <<jme3/intermediate/appsettings#,AppSettings>>.
  ====
  
  
  
  == Default Input Mappings
  
  The following default navigational input actions are mapped by the default `flyCam` control in a SimpleApplication: You can use these mappings for debugging and testing until you implement custom <<jme3/advanced/input_handling#,input handling>>.
  [cols="2", options="header"]
  |===
  
  
negative.code: 
  a|context +
  getContext()
  a|The application context contains the renderer, xref:jme3/intermediate/appsettings.adoc[AppSettings], timer, etc. Typically, you do not directly access the context object.
  
  a|inputEnabled
  a|this internal boolean is true if you want the system to listen for user inputs, and false if you just want to play a non-interactive scene. You change the boolean using xref:jme3/intermediate/appsettings.adoc[AppSettings].
  
  a|keyInput, mouseInput +
  joyInput, touchInput
  