- Type Parameters:
T- the type of the wrapped value
- All Superinterfaces:
- All Known Subinterfaces:
- All Known Implementing Classes:
Bindingcalculates a value that depends on one or more sources. The sources are usually called the dependency of a binding. A binding observes its dependencies for changes and updates its value automatically.
While a dependency of a binding can be anything, it is almost always an
ObservableValue allowing to use it in another binding.
With that one can assemble very complex bindings from simple bindings.
All bindings in the JavaFX runtime are calculated lazily. That means, if a dependency changes, the result of a binding is not immediately recalculated, but it is marked as invalid. Next time the value of an invalid binding is requested, it is recalculated.
It is recommended to use one of the base classes defined in this package
DoubleBinding) to define a custom binding, because these
classes already provide most of the needed functionality. See
DoubleBinding for an example.
- JavaFX 2.0
- See Also:
Method SummaryModifier and TypeMethodDescription
dispose()Signals to the
Bindingthat it will not be used anymore and any references can be removed.Returns the dependencies of a binding in an unmodifiable
voidMark a binding as invalid.
isValid()Checks if a binding is valid.
Methods declared in interface javafx.beans.Observable
Methods declared in interface javafx.beans.value.ObservableValue
addListener, flatMap, getValue, map, orElse, removeListener
isValidboolean isValid()Checks if a binding is valid.
invalidatevoid invalidate()Mark a binding as invalid. This forces the recalculation of the value of the
Bindingnext time it is request.
getDependenciesObservableList<?> getDependencies()Returns the dependencies of a binding in an unmodifiable
ObservableList. The implementation is optional. The main purpose of this method is to support developers during development. It allows to explore and monitor dependencies of a binding during runtime.
Because this method should not be used in production code, it is recommended to implement this functionality as sparse as possible. For example if the dependencies do not change, each call can generate a new
ObservableList, avoiding the necessity to store the result.
- an unmodifiable ObservableList of the dependencies
disposevoid dispose()Signals to the
Bindingthat it will not be used anymore and any references can be removed. A call of this method usually results in the binding stopping to observe its dependencies by unregistering its listener(s). The implementation is optional.
All bindings in our implementation use instances of
WeakInvalidationListener, which means usually a binding does not need to be disposed. But if you plan to use your application in environments that do not support
WeakReferencesyou have to dispose unused
Bindingsto avoid memory leaks.