Hello!

My name is Sean in the real world and I tend to go by 'WoodlandSpirit' wherever I can in cyberspace.

Been exposed to electronic gaming and computing since a very early age with the Atari VCS as a starting point so tend to have a good technical/logical background. By the time the 16-bit machines started to make an impact I was in primary/just going into secondary school and started my venture into programming with STOS on the Atari (AMOS on the Amiga) in my spare time. We did computers at school then but didn't really have any strong programming orientation but I pushed on doing IT through college moving onto more advance languages and landing myself a development job.

However the company was a bit of a two bit operation, things went south, things were a struggle and I just... stopped... didn't feel I could code in any serious manner anymore. The years go by, I go from one tangent to another to where we arrive today and after some soul serching I've com to realise I still want to 'code creatively'.

As with all things the development world doesn't stand still, I can still get my head round the more advanced languages but I'm very rusty and now with 1001 different places to start, raw languages with SDKs, helper libraries, bespoke game engines etc., it just leaves you a bit bewilded on where to knuckle down and I came to a point where I just need to sit down and get coding to get the juices flowing again... and FUZE4 enables me to do just do that, spare half hour with a quick thought, grab hold of the Switch, Bob's ya uncle!

With the throwback to my STOS days I've already got the start of a twin stick shoot on the go, loving the simplicity and accessibility and you bet I'm getting my 10 year old on board as well!

I'll likely go onto more advanced solutions again in time as my diverted journey is rebooted but FUZE4 is giving my that nice jump start and will likely always serve as a tester of ideas and quick thoughts. I very much plan to share projects with everyone as I go along.

Thank you

I don't know if this has been discussed before. But I was able to simulate a switch feature by using a loop and making sure I break on each condition.

loop if x < 1 then do_something() break endif if x < 5 then do_something_else() break endif // put the default options here since they don't match any conditions default() break // don't forget to break here repeat

The coolness of doing this is that if you have a large number of exclusive possibilities that you are testing for you can exit the checking as soon as you find the right one. Or if you're dealing with a deeply nested if .. then .. else this can cut down the depth.