Conditions that rely on the same bindings as their containing trigger use out of date values


Consider the following trigger:

< t:PropertyChangedTrigger Binding="{Binding SomeProperty}" >
< t:InvokeCommandAction ... >
    < t:Condition LeftOperand="{Binding SomeProperty}" ... >
When the property changes, the trigger fires, but the binding within the Condition element hasn't updated its value.

Conditions need to somehow refresh their binding values when being tested.


MikeGoatly wrote Oct 10, 2012 at 10:08 AM

I give up with the XML formatting... you get the idea

wrote Feb 14, 2013 at 12:35 AM