visual event editor

it possible to see that something like this

<img src="http://i.msdn.microsoft.com/Bb483024.VPLScreenshot(en-us,MSDN.10).jpg">

dataflow

a setup like that would get UNBELIEVABLY messy and hard to organize/debug with large games.

and no, it's not possible to display the event sheet like that.

I agree with Davio.... If you have a large project, that could clutter it up BADLY making everything confusing and hard to access.

Construct already has a great event editor anyway.

I have to agree with everyone else. While it might be even more understandable than an ordinary event, look at how much room it takes! An entire screen, and for what looks like one event!

Assuming you can scroll horizontally and vertically, a full game like that would have a massive "field" of randomly placed flowchart tools. Events at least are linear - you can only scroll up and down, not to mention more compact - so it's a lot easier to find things.

Agreed too, while it can look purdy sometimes. I really don't need yet another program that looks like this once you start delving into things.

<img src="http://steamgauge.com/misc/construct/annoying.jpg">

It makes my head hurt, lol.

Though I admit for simple things it can be useful and easy to understand, but yeah it's painful when it gets to complex stuff.

Perhaps for small tasks like setting up fx. What would be really cool is something like this used to set up timelines, hell why not take advantage of the connection lines, and make a path object out of it.

Perhaps for small tasks like setting up fx. What would be really cool is something like this used to set up timelines, hell why not take advantage of the connection lines, and make a path object out of it.

Hmm, spline based paths and keyframing. What a lovely Christmas present that would make, *smiles at the devs hopefully*

I've been using the UDK a bit and I'm familiar with the 'Kismet' tool they have which allows you to make small programs to control things like openning a door. The main advantage to such a thing is sequential stuff. Its really easy to setup a system where you press a switch, the door opens, it waits for 5 seconds, then the door closes.

<img src="http://dl.dropbox.com/u/939828/flowchart1.PNG">

Whereas with traditional programming methods you do something like:

OnSwitchPress

--- Tell the door to play open animation

On door open animation finished

--- Initialise a timer

On timer finished

--- Tell the door to close

And the problem with this is other 'features' can clash. For example, lets say you have another switch which perminently opens the door

OnPerminantSwitchPress

--- Tell the door to play open animation

But now you have a problem... 'On door open animation finished' will be triggered! So as a result you make a variable inside door like 'lockedForever' and you end up with this:

//Feature 1

OnSwitchPress

--- Tell the door to play open animation

On door open animation finished

perminent is not true

--- Initialise a timer

On timer finished

--- Tell the door to close

// Feature 2

OnPerminantSwitchPress

--- Tell the door to play open animation

--- Set door to 'perminent'

But as you can see Feature 2 affects Feature 1...so it can all get ugly.

Whereas with a flowcart you create this:

<img src="http://dl.dropbox.com/u/939828/flowchart2.PNG">

Door is the same object, but a different instance in the programming.

So the flowchart method can be quite handy.

interesting stuff

ok, so I geuss the ultimate solution would be an option for a special "flowchart" block for the event sheet. Clean events for regular stuff, flowcharts for annoying to set up variable triggered clutter.

Yeah lets go green, and recycle events.

Actually, put it that way and it does sound pretty useful.

However, is there any chance something like this could actually be implemented?

I doubt a feature Like this could be implemented for construct 1 but maybe 2.0 it could be implemented.

Well I still personally dont like visual editors like this because I think you spend too much time organising your diagram and they can easily get confusing to read.

One idea me and Ashley have been discussing is a 'wait until'...for example:

<img src="http://dl.dropbox.com/u/939828/flowchart2.PNG">

This could be represented in events as:

<img src="http://dl.dropbox.com/u/939828/events2.PNG">

(mockup only)

But yeah I'm not sure whats clearer, the events or the flowchart...I personally think it's easier to read the events. Its like 'ah okay so you press the trigger, the door opens, then you wait 5 seconds after its opened, and then it closes' whereas the flowchart its like where do you start reading from...

It's not a useless feature, but only not obligatory.