XAML trigger as StaticResource?

I imagine that this is because resources are loaded first.

I imagine that this is because resources are loaded first. So in this case, WPF would try to load your trigger before any control it might be associated with. Then the trigger value can't be evaluated at that time.

But that need to be confirmed :).

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.