|
|
@@ -187,7 +187,7 @@ public class MyAppState extends AbstractAppState {
|
|
|
----
|
|
|
|
|
|
|
|
|
-=== BaseAppState
|
|
|
+== BaseAppState
|
|
|
|
|
|
|
|
|
A new link:http://javadoc.jmonkeyengine.org/com/jme3/app/state/BaseAppState.html[BaseAppState] class was introduced as part of the link:https://hub.jmonkeyengine.org/t/jmonkeyengine-3-1-alpha-4-released/35478[updates] being made to the AppState interface. AbstractAppState is the most minimal of the minimal implementations of the AppState interface. You essentially still need to do everything yourself, including getting the funky enable/disable/initialized/terminate logic right. Now you just extend BaseAppState and you get onEnable() and onDisable() already worked out for you.
|
|
|
@@ -242,8 +242,8 @@ Notable BaseAppState changes are as follows:
|
|
|
* You no longer need to call super.initialize(stateManager, app) because it is now called by BaseAppState upon initialization for you.
|
|
|
* You no longer have to cast SimpleApplication to have access to AssetManager, AppStateManager, and you can even get a State directly. The getters getApplication(), getAssetManager(), getState(type) and their methods are available to you immediately. However, you still have to cast SimpleApplication to get rootNode.
|
|
|
* You no longer call super during cleanup, its done for you now.
|
|
|
-* It is now safe to do all initialization and cleanup in the onEnable()/onDisable() methods.
|
|
|
-* Cleanup and setEnabled now have logging built in.
|
|
|
+* It's now safe to do all initialization and cleanup in the onEnable()/onDisable() methods.
|
|
|
+* Cleanup and setEnabled now have logging built in.
|
|
|
|
|
|
You use BaseAppState as you would AbstractAppState, other than mentioned above, and which one you use is entirely up to you. However, BaseAppState makes your life easier and is the recommended one to use now.
|
|
|
|
|
|
@@ -325,4 +325,3 @@ public class MyAppState extends AbstractAppState {
|
|
|
}
|
|
|
|
|
|
----
|
|
|
-
|
mitm001