xyanid / bindablefx Goto Github PK

Currently when a IPropertyBinding does not yet have a underlying property, the setValue() method will memorize the value and set it once the property is available. So imagine the following scenario:

1. IPropertyBinding gets bound to another Property.
2. IPropertyBinding does not yet have a property of its own
3. The other property gets set, which would memorize the value
4. As soon as the IPropertyBinding gets its property, the value of the property is adjusted

In most cases this does not seem to be problematic but imagine the following:

1. A listview contains items and displays some of the field (e.g. a name of a person)
2. The IPropertyBinding gets bidirectional bound against the textfield
3. No item is yet selected
4. The textfield is activated and text is entered
5. An item in the listview is selected
6. The bound value of the item would change because the textfield was previously adjusted.

Solution would be to make the memorize functionality optional and disable it by default. So in the above scenario, the value of the selected item would not change, but in fact the value in the textfield would change.

Implement a ListBinding that does allow for the following actions:

• Map all the values in a list to a single value
• Map all the values in a list to a list of different values
• Synchronize the content of two lists

The current FluentAPI should be reworked, since it is sometimes hard to understand the intend of a statement. This should include the renaming of methods and even the attempt to make a base, root Listeners so that something like this would work waitFor(a.bProperty).bind(B::xProperty, x);