Hi guys. Okay, back to blue. I have everything from the main program hooked up to all the dialogs and edit screens now. It’s a necessary evil with programming that you spend 50% of your time writing code to support the UI. You need to make sure when the user leaves an edit field that you grab the data entered, validate it, update the object, whatever and carry on. This has to be done for everything and it’s just time consuming. What it provides to you is a near idiot proof way of editing values or manipulating objects in the program. Otherwise, it would be a big screen with no buttons and you’d have to figure it all out yourself. A program like blueprint needs to provide visual feedback as to what you’re doing or else you don’t know what’s going on (like if an object goes offscreen, just because you can’t see it doesn’t mean it’s not there). In any case, all that’s done now so I’m in the final stretch with regards to making sure the objects are exporting, the sprites are updating correctly and everything is working end-to-end.
As you may (or may not) have noticed, the recent screenshots of the program bear little resemblance to the tutorial that’s online. Thats one of the reasons why I’ve held back on doing more tutorials and releasing interim versions. Things have been in a state of flux so I didn’t want to have to try to play catchup for the next few months. Once I get this version off to the testers I’ll consider most of the UI and workflow locked down and only technical problems (behind the scenes) are left to fix so I’ll spend that time writing some new tutorials that will help you ramp up on the new version and walk through various techniques like lighting, materials, textures and editing objects.