AppState Question

Just a Question.
If i had more than one class running, that is an AppState and is implementing some kind of parent class. If i now called that superclass with the stateManager like this:


Would there be any class be called, implementing my superclass ?
Is it just taking one ? And if it is taking one, which would it take ?

It would get the first one attached.

1 Like

Is there a good tutorial on how to use theese AppStates ordinary ?
How to manage the GameState itself during my runtime is still a question.
My solution works, but i think i shouldn’t do it this way …
So i am looking on how to setup it correctly.
There has to be change in what it is doing at some point of time, some nodes have to be attached and detached and some values be changed, i’ll see.
And i don’t want to make it too complicated.
Mine is now very easy, but it’s a little bit messed up and i want to clean it.
How are you using gamestates like “Loading, Menu, Login, Game, Quit” ?
somewhere you have to talk with each other, if it isn’t just a box rotating around a sphere…

If you want to see how I personally use app states then there are many places to look.

You can look at the code for Monkey Trap which was a partial game I wrote using Zay-ES and Lemur.

You can also look at SimArboreal:

Or the IsoSurface demo:

All of which use app states heavily… though I don’t know if any of them specifically have loading screens. (Monkey Trap might.)

None of my stuff uses nifty so you’ll be on your own for that… or whatever help others might provide. But those apps might give you an idea of how to break apart things into app states and have them easily refer to each other.

1 Like

Thanks. That’s will help ! :wink: I got that nifty thing now, i think. There are small portions left, but that isn’t a problem at this point of time :wink: I just want to understand, how to use this stuff as efficient as possible for my purposes.