Refactor ContextHolder

I suggest making ContextHolder abstract only providing Get/Set-Access to Context and Type. As well as using an event for ContextChanged-Notifications. Reason: If I have multiple DataContexts that may be relevant for different things in the game I cannot use this because I cannot reference other DataContexts from one GameObject.

public class ContextPointer : ContextHolder
{
    public ContextHolder ContextHolder;

    public override object Context
    {
        get
        {
            return ContextHolder.Context;
        }
        set { }
    }
    public override Type ContextType
    {
        get
        {
            return ContextHolder.ContextType;
        }
        set { }
    }

    protected void OnEnable()
    {
        ContextHolder.ContextChanged += ContextHolder_ContextChanged;
    }
    protected void OnDisable()
    {
        ContextHolder.ContextChanged -= ContextHolder_ContextChanged;
    }

    private void ContextHolder_ContextChanged()
    {
        OnContextChanged();
    }

    protected override void OnContextChanged()
    {
        // Update child bindings as context changed.
        var uiBindings = this.gameObject.GetComponentsInChildren<Setter>(true);
        foreach (var binding in uiBindings)
        {
            binding.OnContextChanged();
        }
        var providers = this.gameObject.GetComponentsInChildren<DataProvider>(true);
        foreach (var provider in providers)
        {
            provider.OnContextChanged();
        }
        var commands = this.gameObject.GetComponentsInChildren<Command>(true);
        foreach (var command in commands)
        {
            command.OnContextChanged();
        }
        base.OnContextChanged();
    }
}

Or, if this is not a practical approach try to make Bindings independent from their parents (i.e. allow Bindings from root\Object1 to root\Object2 where Object1 has the ContextHolder)

Comments (5)