All the `xBinding` functions returns bindings, not...
# tornadofx
e
All the
xBinding
functions returns bindings, not properties. If you think about it, how would a calculated property behave if it was writable? Should it write back into the underlying properties perhaps? TornadoFX actually supports these kinds of proxy properties as well, but I suspect that's not what you're after. Are you wondering why you get
ObjectBinding<BigDecimal?>
instead of
ObjectBinding<BigDecimal>
? The reason is that the underlying property might be null, and if so we might want to return null from the calculated binding as well. This normally doesn't create an issue, the property is still observable and would carry the correct calculated
BigDecimal
value.