public class TestAppStateLifeCycle.TestState extends AbstractAppState
initialized| Constructor and Description |
|---|
TestState() |
TestState(java.lang.String id) |
| Modifier and Type | Method and Description |
|---|---|
void |
cleanup()
Called by
AppStateManager when transitioning this
AppState from terminating to detached. |
void |
initialize(AppStateManager stateManager,
Application app)
Called by
AppStateManager when transitioning this AppState
from initializing to running.This will happen on the next iteration through the update loop after AppStateManager.attach(com.jme3.app.state.AppState) was called. |
void |
postRender()
Called after all rendering commands are flushed.
|
void |
render(RenderManager rm)
Render the state.
|
void |
stateAttached(AppStateManager stateManager)
Called by
AppStateManager.attach(com.jme3.app.state.AppState)
when transitioning this
AppState from detached to initializing. |
void |
stateDetached(AppStateManager stateManager)
Called by
AppStateManager.detach(com.jme3.app.state.AppState)
when transitioning this
AppState from running to terminating. |
void |
update(float tpf)
Called to update the
AppState. |
getId, isEnabled, isInitialized, setEnabled, setIdpublic void initialize(AppStateManager stateManager, Application app)
AppStateAppStateManager when transitioning this AppState
from initializing to running.AppStateManager.attach(com.jme3.app.state.AppState) was called.
AppStateManager will call this only from the update loop
inside the rendering thread. This means is it safe to modify the scene
graph from this method.
initialize in interface AppStateinitialize in class AbstractAppStatestateManager - The state managerapp - The applicationpublic void stateAttached(AppStateManager stateManager)
AppStateAppStateManager.attach(com.jme3.app.state.AppState)
when transitioning this
AppState from detached to initializing.
There is no assumption about the thread from which this function is
called, therefore it is unsafe to modify the scene graph
from this method. Please use
AppState.initialize(com.jme3.app.state.AppStateManager, com.jme3.app.Application)
instead.
stateAttached in interface AppStatestateAttached in class AbstractAppStatestateManager - State manager to which the state was attached to.public void update(float tpf)
AppStateAppState. This method will be called
every render pass if the AppState is both attached and enabled.update in interface AppStateupdate in class AbstractAppStatetpf - Time since the last call to update(), in seconds.public void render(RenderManager rm)
AppStateAppState is both attached and enabled.render in interface AppStaterender in class AbstractAppStaterm - RenderManagerpublic void postRender()
AppStateAppState is both attached and enabled.postRender in interface AppStatepostRender in class AbstractAppStatepublic void stateDetached(AppStateManager stateManager)
AppStateAppStateManager.detach(com.jme3.app.state.AppState)
when transitioning this
AppState from running to terminating.
There is no assumption about the thread from which this function is
called, therefore it is unsafe to modify the scene graph
from this method. Please use
AppState.cleanup()
instead.
stateDetached in interface AppStatestateDetached in class AbstractAppStatestateManager - The state manager from which the state was detached from.public void cleanup()
AppStateAppStateManager when transitioning this
AppState from terminating to detached. This
method is called the following render pass after the AppState has
been detached and is always called once and only once for each time
initialize() is called. Either when the AppState
is detached or when the application terminates (if it terminates normally).cleanup in interface AppStatecleanup in class AbstractAppState