SystemStateMachine

[Neil Manuell]

has anyone written a FSM for adding removing systems from the engine similar to the EntityStateMachine

[Richard]

Hi Neil

It's been in my mind to do so, but I haven't done it, no. I'd be happy to help out if you want to do it.

Richard

[Neil Manuell]

cool - I was thinking of using the EntityStateMachine as a template.

some questions

Is there any reason why you would:

1) ever have more than one instance of a system registered in the engine at a time?

2) need a withType inequivalent?

can you think of any gotchas that may occur from this approach?

--
You received this message because you are subscribed to a topic in the Google Groups "Ash Framework" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ash-framework/O9UOZxm-Q4M/unsubscribe?hl=en.
To unsubscribe from this group and all its topics, send an email to ash-framewor...@googlegroups.com.
Visit this group at http://groups.google.com/group/ash-framework?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Richard Lord]

I would say no to both of those. Systems shouldn't retain game state so it should be fine to reuse the same instance throughout.

R

You received this message because you are subscribed to the Google Groups "Ash Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ash-framewor...@googlegroups.com.

[Neil Manuell]

that's what I thought,

so i was thinking withSingleton withInstance and withMethod

neil