@mrl said in Xamarin's contiuing barrel of cross-platform, XML-encoding fut the wuckery:
The question is: why do you need a converter for that at all? In UWP there are only two states, why tf do I need to write a whole class for that?
Because it's based on WPF, which has three values for visibility, and presumably with XAML Standard UWP will have the 3 visibility states again as WPF, UWP and Xamarin.Forms (plus others) will all be using the same XAML components.
As for INotifyPropertyChanged, you typically have a helper function for that which allows very simple view models. If you keep repeating boilerplate code, you are doing it wrong.
Oh yes, you have the magnificent helper method that raises notification event. Such wow. Thanks to it, this property declaration:
public MyThing { get; set; }
still looks like this:
private myThing;
public MyThing
{
get { return myThing; }
set
{
if(myThing != value)
{
myThing = value;
Notify();
}
}
}
For. Every. Fucking. Property.
Every single class I write that needs to implement INotifyPropertyChanged implements a Observable base class (usually included with MVVM frameworks) that turns it into
private myThing;
public MyThing
{
get { return myThing; }
set { Set(ref myThing, value); }
}
And I'd much rather that tiny bit of boilerplate, plus all the benefits of binding and MVVM than the crapton of work that's typically required by doing it in the codebehind instead.