Version 1.0.10

• Use OnValueChanged without parameter in ContextDataProvider instead of obsolete version

• Clean up RoundToNearestOperation

• DataBindingOperator only IsInitialized when the Init method is called. Otherwise it may not have added its bindings and return the default value.

• Add example of two way bindings (input field and slider)

• Add utility property to NotifyPropertyChangedDataContext to easily access wrapped data object

• Issue #53 Wrap INotifyPropertyChanged class inside NotifyPropertyChangedDataContext automatically in ContextHolder (https://bitbucket.org/coeing/data-bind/issues/53/automatically-wrap-inotifypropertychanged)

• Issue #52 Using NETFX_CORE define instead of UNITY_WSA/UNITY_METRO (https://bitbucket.org/coeing/data-bind/issues/52/some-scripts-are-not-compilable-under)

• Issue #46 Use InputFieldTextProvider/InputValueProvider and ContextDataUpdater instead of obsolete InputFieldTextGetter/InputValueGetter (https://bitbucket.org/coeing/data-bind/issues/46/the-example-stringtoupperstringunity-still)

• Add unit tests to check if a property in a sub context that implements INotifyPropertyChanged can be accessed and triggers value changes

• Issue #51 Use !field.IsPublic instead of field.IsPrivate. field.IsPrivate flag is always false (https://bitbucket.org/coeing/data-bind/issues/51/a-unity-2017-universal-windows-platform)

• Add TypeInfoUtils to have WSA specifics in one place

• Show any list instead of only Collections for ContextHolder in inspector

• Update value of ContextDataProvider when value inside context changed

• Add MeshFilterMeshSetter

• Change folder name from NotifyPropertyChangedExample to NotifyPropertyChanged to be consistent with former examples

• Rename DataContextNode to DataNode and use Branch and Leaf data nodes to build data tree

• Use INodeValueObserver to unify observation of a node value, either with a DataProvider or INotifyPropertyChanged mechanic

• Rename ContextNode to DataContextNodeConnector

• Wrap INotifyPropertyChanged class when selected as context type and context should be created automatically

• Move out some stuff from ContextHolderEditor

• Draw data class in inspector when NotifyPropertyChangedDataContext is used as a wrapper

• Add option to only trigger ValueChanged of an InputFieldTextProvider when editing ended

• Add non-generic version of CollectionDataBinding

• Move common code into BranchDataContextNode and static methods into DataBindingSettingsProvider and out of DataContextNode. Make as much as possible private for DataContextNode

• Issue #48 Special case for getting paths for MasterPath path dropdown (https://bitbucket.org/coeing/data-bind/issues/48/wrong-paths-in-drop-down-of-data-bindings)

• Add example for usage of MasterPath

• Issue #26 Show paths for custom serializable classes as well (https://bitbucket.org/coeing/data-bind/issues/26/also-show-paths-for-non-context-classes-in)

• Add header to DataContextNode

• Issue #47 Use Equals to check for value equality instead of == operator (https://bitbucket.org/coeing/data-bind/issues/47/context-invokes-callbacks-even-if-value-of)

• Add number increase/decrease buttons to NotifyPropertyChangedExample

• Specify data context type of context holder in NotifyPropertyChangedExample

• Use concrete class instead of NSubstitute in NotifyPropertyChangedDataContextTest

• Use INotifyPropertyChanged classes as context types and create paths for those types

• Cache data context paths in PathPropertyDrawer

• Move data node handling into DataTree to avoid code duplication

• Rename NotifyPropertyChangedContext to NotifyPropertyChangedDataContext

• Add unit tests for NotifyPropertyChangedContext

• Add example to test NotifyPropertyChanged data contexts

• Add wrapper for data context that use INotifyPropertyChanged instead of data properties

• Add null reference check to EnumGetter to avoid an exception

• Add base class for a data provider that provides a constant value

Other Resources