entity.onUpdateStop( ) call to pass id string to event...

[ucm]

[ucm]

Forgot to mention the biggest benefit is that the function would first execute any code immediately at the .updateStop call and ''then'' the object/entity/scene would stop it's update passes until a .updateStart() function is called to 'restart' the update passes...

Then something like having a flag set for whether or not the onFirstUpdate should get called 'again' on a .updateStart() call... something like .callFistUpdateOnUpdateStart = true/false ...... or something xD

[StarFire]

[ant0N]

Thank you NightHawk! now I understand how it works!!!

[StarFire]

Pleased to have helped

[ucm]

[StarFire]

[ucm]

umm are you saying that you need to manually create the various game states during engine build time in the C++ ide ?

hmmmmmm.... well if we could create our own gamestates then that would be a major advantage....

could you program a document-wide setting for 'user-defined states' then at runtime, the player first checks out the states listed in the settings and then links all the appropriate event handler functions to the user-defined states?

lol i 'think' i know what i'm talking about buuuut i probably don't xD

[StarFire]

Yes in time there will be a way, we could have a number of user states such as onUpdate_User1

[ucm]

[StarFire]

The states are only active if they are called, until then they lay dormant and add no load to the game( invisible to the system). If you just used the game main state which is the basic state onUpdate(), onkeyDown() etc the other states don't exist until setState is called. You don't need to add their functions to the script unless you want to activate them. This is designed so you don't need to mange them yourself.

[Shando]

Just a quick question on States......

I presume when a State has already been run, and you've changed to another State, that if you change back to the initial State it will start as if it had never run before?

e.g:

State1 runs
State2 called so State1 exits
State1 called so State2 exits <-- I am assuming that State1 does not remember anything about it's previous life???

Regards

Shando

[SolarPortal]

It does, but if you want to change/reset, use that states onEnter() function.

[Shando]

Hi SolarPortal,

So, if I had some Global Variables that existed in State1, they would be persistent across all States?

Regards

Shando

[StarFire]

yes, the scripts global var is persistent across all states, its only the update loops,enter + exit that change.

hope this helps

[Shando]

[StarFire]

Hey Shando thank you for the request
I will give this some thought but for now we have added it our feature request list. It sounds like it will be possible, as we added many extra states but have not activated them, if you are happy keeping the generic naming (yes comments our our friend, especially in 6 months time when we have to go back over the code!) we should be able to expose them to lua for you.

[Shando]

Hi NightHawk,

Yes, I'd be happy with generic naming - what does the rest of the community think????

Regards

Shando

[Shando]