You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
According to the documentationBindableObject.CoerceValue should force reevaluation when called. Am I misunderstanding what is meant by reevaluating? I'd assume the property value would be updated after BindableObject.CoerceValue is called.
However, when I test, the values does not change. The returned value from my delegate is returning a new value.
As far as my limited understanding of the source code in MAUI, in BindableObject.CoerceValue the delegate is invoked, but the returning value is never used. Should BindableObject.CoerceValue not check if CoerceValue delegate property is set and then set the bindable property value from its result?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
According to the documentation
BindableObject.CoerceValue
should force reevaluation when called. Am I misunderstanding what is meant by reevaluating? I'd assume the property value would be updated afterBindableObject.CoerceValue
is called.However, when I test, the values does not change. The returned value from my delegate is returning a new value.
As far as my limited understanding of the source code in MAUI, in
BindableObject.CoerceValue
the delegate is invoked, but the returning value is never used. ShouldBindableObject.CoerceValue
not check ifCoerceValue
delegate property is set and then set the bindable property value from its result?Beta Was this translation helpful? Give feedback.
All reactions