Version 1.0.11

• Call first Enable of a data binding operator in the Start method instead of OnEnable to make sure that all other scripts had time to initialize in their Awake method (Unity may call OnEnable of an object before the Awake method of other objects was called, see https://forum.unity.com/threads/onenable-before-awake.361429/)

• Add small SpriteLoading example that also shows the issue #59 (invalid warning from SpriteLoader)

• Issue #58 Add indexer to Collection class

• Issue #63 Add warning if more than one settings objects are found and none is called like the default one

• Issue #63 Use any DataBindSettings object found in resources when not found at default path

• Issue #63 Made DataBindSettings editable again

• Issue #62 Show items of any IEnumerable in ContextHolderEditor and add buttons to remove/add for ICollection members (which includes Collection class)

• Issue #34 Add error when target binding doesn't receive an object of the expected type

• Use GameObjectItemsSetter instead of LayoutGroupItemsSetter and flag LayoutGroupItemsSetter as obsolete

• Use virtual method NotifyContextOperatorsAboutContextChange instead of IContextHolder interface

• Only update context data in ContextDataUpdater if active and enabled

• Only use Coroutine for delayed value initialization in DataContextNodeConnector if mono behaviour is enabled

• Issue #60 Only register listener when a valueChangedCallback is set, otherwise an initial value 'null' is returned which changes the context value incorrectly

• Issue #60 Add example that shows a bug when switching the context of a context holder

• Issue #49 Delay data update when context changed till end of frame as there may be multiple data context node connectors that have to update their context first

• Use MonoBehaviour a data binding and data context node connector belong to instead of game object

• Add test case for issue #49

• Issue #45 Make GetValue and SetValue of a context work with struct members

• Issue #56 Make Unity callbacks protected in DataBindingOperator, so there is at least a warning when overriding them instead of the virtual methods (A derived class should use the virtual methods (Init, Deinit, Enable, Disable) instead of the Unity callbacks, so the initialization order remains correct.)

Other Resources