WPF: Condition Binding versus Property, XamlParseException using either?

The API in this case is confusing Condition is used for two different types of multi-triggers, and the properties used are different. When using MultiTrigger you will use the Property and Value properties. When using MultiDataTrigger (which is what you need), you specify a Binding and a Value So, if you just switch your code to use a MultiDataTrigger you'll be good to go.

The API in this case is confusing. Condition is used for two different types of multi-triggers, and the properties used are different. When using MultiTrigger, you will use the Property and Value properties.

When using MultiDataTrigger (which is what you need), you specify a Binding and a Value. So, if you just switch your code to use a MultiDataTrigger, you'll be good to go.

Great, thanks! I no longer get the XamlParseException, though I must not have the last Condition right yet, because my setters don't work anymore on enabled ListView items. – Sarah Vessels Jan 10 at 19:08.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.