Apologies, I'm going to take this post off-topic and talk a bit more. These diagrams are just so valuable, I have to share a bit more.
I've always been one for Rapid Development (RAD) - throw some code in and see if it works, then throw the next bit in. I always code the less attractive stuff first, then bring it to life later. This method has numerous advantages but it can also lead to all sorts of problems because visually there is very little to see, and what you coded may not be what happens.
So...these diagrams add visualisation to code where there is nothing to see, and makes sure that you are a lot closer to what you envisaged.
Secondly, it's so much easier to track down flaws in your logic before you even start.
Thirdly, it makes you code in state machine format. I know not everybody likes it, but I recommend everyone in the procedural (basic) coding world gets to like it. It's the easiest way to move towards simulated event-driven programming (
opens up a door for another off-topic conversation).
Fourthly, it's just a damn good way to get your ideas on virtual paper. I'm trying to create a gameplay state machine that can handle a sequence of screens. Some are quiz questions, some are intro screens, some are adverts and so on. This visual method is helping me to work out how I can use the same code to deliver questions, answers, ads and intros without differentiating between them.
I'll stop going on and on now!
Disclaimer: I do not use any regimental method and I am no expert on coding methodologies. I simply use what works for me.
