I think it must be due to compatibility with WPF. WPF has an additional
value for Visibility called "Hidden" which can be useful as the UI element
retains it's dimensions.
The weird thing is that Silverlight doesn't have "Hidden" I think. I
don't find the need for a converter a problem. You code it once and job
done.
On Fri, 12 Mar 2010 03:56:20 +0530 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
