向实体/组件系统添加功能

Question

I'm attempting to write my own Entity/Component System from scratch in C# and I'm stuck on where/how to implement some functionality.

Edit: I figured out how where I'm going to add functions like Move() and Jump().

public static class Actions
{
    public static void MoveUp(EntityManager entityManager, int EGUID) {}
    public static void MoveDown(EntityManager entityManage, int EGUID {}
}

I can add them to a collection like so:

KeyboardController kbController = entityManager.GetComponent<KeyboardController(1);
kbController.KeyBindings.Add(Keys.Right, new Dictionary<KeyStateES, Action<EntityManager, int>());
kbController.KeyBindings[Keys.Right].Add(KeyStateES.Held, Actions.MoveUp);

And now I'm able to move the Entity around quite easily with key bindings. However, it's still not quite ideal because:

• I can't bind more than one Method to a Key.
• I'm forced to pass the Method Arguments in the InputManager class.

This is a problem because sometimes I'll want a key to perform multiple unrelated tasks and because it seems really silly for my InputManager to be the one passing the arguments for the methods. Ideally, I would like it so that a KeyDown, KeyHeld, or KeyReleased event is fired and only the Controllers with the particular key(s) bound respond to the event and execute their associated Methods.

Answer 1

After that you changed X and Y coordinates o the Entity using specific component, you just redraw scene, and Entity will appear into the a new position. Where is actually the problem. ?

You have an Entity that is transformed in any possible way with (say) PositionComponent , RotationComponent , ScalComponent , TextureComponent and so on, but have simple Redraw() method which renders all Entites on the scene in visible frustrum within a current state of each one.

Answer 2

How about a tree of types focused on these high-level behaviors?: ie a Jump class would, given an object, know how to make it jump. Jump might be derived from Move if there is sufficient commonality, etc. More complex behaviors would then be composed of simpler behaviors heirarchically.