CStateSys

Jookia · Post by **Jookia** » Wed Jun 24, 2009 10:03 am

This is a state machine that works well and doesn't afraid of anything.
Demo includes source code, an unfinished options dialog and sydney.mdl and Doxygen for CStateSys.h.

Comments are accepted.

DOWNLOAD

Brainsaw · Post by **Brainsaw** » Wed Jun 24, 2009 10:11 am

Damnit ... I just wrote my state machine yesterday.

Jookia · Post by **Jookia** » Wed Jun 24, 2009 10:13 am

This allows parent->children relationships.

Brainsaw · Post by **Brainsaw** » Wed Jun 24, 2009 11:15 am

Mine is pretty simple. It is a better version of the state machine I used in two of the demo applications of my IrrODE wrapper (IrrOdeCar, IrrOdeMarble), with a few more things in mind. I think I'll put it online here as soon as I got around to create something more than the switch-some-guis-test

. But still ... it's very simple.

vitek · Post by **vitek** » Wed Jun 24, 2009 8:02 pm

I shared some state machine code a while back. You can find it here.

Code: Select all

if(event.GUIEvent.EventType == gui::EGET_BUTTON_CLICKED)
{
  if(name == "Quit")
    CQuitState* quitState = new CQuitState(manager, this);
  else if(name == "Broken Options")
    COptionsState* optionsState = new COptionsState(manager, this);
}

Who cleans up the memory allocated here? As far as I can tell, the states do not register themselves with the manager or set themselves as the current state, so they are probably leaks.

Ion Dune · Post by **Ion Dune** » Wed Jun 24, 2009 8:33 pm

I think this state machine is a pretty cool guy. eh kills aleins

Always nice to see 4chan on irrlicht. But I think "works well" is a bit of a stretch, considering it crashes when you close the options or quit the application

Jookia · Post by **Jookia** » Thu Jun 25, 2009 1:05 am

Ion Dune wrote:I think this state machine is a pretty cool guy. eh kills aleins

Always nice to see 4chan on irrlicht. But I think "works well" is a bit of a stretch, considering it crashes when you close the options or quit the application

That was a bug that I fixed, I'm working on a more impressive tech demo. Just recompile.

vitek wrote:I shared some state machine code a while back. You can find it here.
Code: Select all
if(event.GUIEvent.EventType == gui::EGET_BUTTON_CLICKED)
{
  if(name == "Quit")
    CQuitState* quitState = new CQuitState(manager, this);
  else if(name == "Broken Options")
    COptionsState* optionsState = new COptionsState(manager, this);
}
Who cleans up the memory allocated here? As far as I can tell, the states do not register themselves with the manager or set themselves as the current state, so they are probably leaks.

The second argument is a parent. Once the parent is destroyed those states get destroyed.

Jookia · Post by **Jookia** » Thu Jun 25, 2009 2:32 am

There, I fixed my very bad example.