Basically what you are doing is assigning the very same instance of a TextBlock to each TabItem. On the first iteration, the TextBlock is added to the first TabItem. On the second iteration, the very same TextBlock is added to the visual tree.
The error message you see is trying to tell you that the TextBlock can't have two parents (there is a joke there somewhere).
Basically what you are doing is assigning the very same instance of a TextBlock to each TabItem. On the first iteration, the TextBlock is added to the first TabItem. On the second iteration, the very same TextBlock is added to the visual tree.
The error message you see is trying to tell you that the TextBlock can't have two parents (there is a joke there somewhere). You can set a template for these, however. A template instructs the TabItem to create a new set of whatever visual you want per item created.
Of course. Even though the net XAML was approximately the same, where in the working case a TextBlock was being inserted for each bound string, the key difference is that a new TextBlock was being generated for each string. In the failing case, I was telling it to use the same one over and over.
Shame on me. – Jerry Bullard Sep 20 '10 at 17:28.
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.