a new node system will make scripting easier.

Nodes can be of type action, trigger or object and have different in- and output connectors.

• object nodes show their connections to their triggers
• triggers and actions show connections to their actions
• property window shows up upon double clicking a node (same window as before)

a connecting line between two connectors only visualizes that action A has a link to action B. How that link works is up to the actions in question. One action might modify another action’s properties directly (‘push-mode’) while another action reads a property of a connected action (‘pull-mode’). Both cases would simply display a line or curve between the two connectors.

a first attempt at rendering nodes inside a clipped area:

along with this change, the base action might be expanded:

each action might get the ability to trigger a remote action, just like the ‘execute’-action did before.

This works exactly like a follow-up action, except that the executed action can be a remote action and doesn’t have to be an immediate child.

Continue reading →

Recently, I’ve implemented a weak pointer class that manages its resource pointer by setting it to NULL in every instance that uses that same resource.

That way, weak pointers allow for notifying anyone who has a pointer to that resource once the resource gets deleted.

Good idea, especially since p407 uses a dynamic editor environment with objects that reference others that might get deleted at any point.

Continue reading →

logic actions of type AND, OR, etc. each take one or multiple input logic actions and alter their internal state.

Optionally, they can have a target, just like any other action.

The main difference is that that target isn’t an object but a trigger or another action that gets triggered when the logic operation’s internal state either hits true or false (configurable).

Continue reading →