Timeline for Game state management techniques?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 7, 2011 at 10:39 | comment | added | Kylotan | You make it sound like a class is more correct than the alternatives, but remember that is subjective. If you start creating too many small classes for things that can be represented more easily by other language constructs then it can obscure the intent of the code. | |
| Jun 7, 2011 at 7:02 | comment | added | vargonian | Yes, I imagine there's a line between going all-out with states and just using a bool/enums when appropriate. But knowing my pedantic tendencies, I'm probably going to end up making almost every state its own class. | |
| Jun 6, 2011 at 12:55 | history | answered | Kylotan | CC BY-SA 3.0 |