Rick's Blog

Added PositionEntity. This file will create a cube and position it.

 

<?xml version="1.0" ?>
<root>
<behavior name="create_cube" >
	<result type="Entity" value="cube1" />
</behavior>
<behavior name="position_entity">
	<parameter type="Entity" source="variable" value="cube1" />
	<parameter type="float" source="constant" value="0" />
	<parameter type="float" source="constant" value="1" />
	<parameter type="float" source="constant" value="2" />
	<parameter type="int" source="constant" value="1" />
</behavior>
</root>

 

Now that I have these 2, I'll work on the UI so that one can make this file via a flowgraph UI.

Got events working now. You would drag on the behavior "attach_entity_event" & the event you want to attach to, like "update_entity", and then link which entity you want to attach to that event. The out connector of that event is where you define the functionality inside that event.

 

The xml would look like:

<root>
<behavior name="create_cube" >
	<result type="Entity" value="cube1" />
</behavior>
<behavior name="attach_entity_event" >
	<parameter type="Entity" source="variable" value="cube1" />
	<parameter type="xml" source="variable" value="event:on_update_1" />
</behavior>
<event name="on_update_1" type="UpdateEntity" >
	<behavior name="test">
	</behavior>
</event>

This looks cool! I had an idea that was similar to this,

 

What's the difference between an Action and an Event? Is an action a function pointer of some sort?

An action is basically a function that you must call in your chain. Think of something like CreateCube(). An event is something that gets called by the game or engine. Think of something like on a collision. LE will call a function callback. This is an event. In the terms of the flowgraph system your "main" function is called automatically and you chain actions together to start your program. Since events get called at random times nothing has to proceed and event. It's the starting point that can happen at any given time when it gets fired.