We use an extension method to solve that. - Caleb Jenkins | 469.867.4552
(sent from my mobile phone) On Mar 11, 2010 4:31 PM, <ton...@tpg.com.au> wrote: Hi all, Does anyone else get annoyed at the extra hastle required to set and bind the Visibility property? I mean, how easy was it in the "old days" to simply set IsVisible=true or IsVisible=false? You didn't need a Visibility to Bool converter, which is extra unneccessary processing, and an extra point of failure if it's forgotten, and more text to make mistakes. I mean, come on, there are only two states. There will never be a third state. Instead of writing in my code: TermTextBox.IsVisible = MyBoolVar; I have to write something like: TermTextBox.Visibility = (MyBoolVar ? Visibility.Visible : Visibility.Collapsed); Does it somehow give it extra contextual meaning for all the extra effort? No. Can there be a third state, somehow semi-visible. No - that would be handled via an opacity or animation. There is only a single meaning! It's Friday, bring it on! Regards, Tony _______________________________________________ ozsilverlight mailing list ozsilverlight@ozsilverlight.com http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
_______________________________________________ ozsilverlight mailing list ozsilverlight@ozsilverlight.com http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
