Absolutely not. Whatever works for you, keep doing that! There is no MVVM police that will come get you. Choosing MVVM will give you some advantages but if you decide you can live without that, that is fine too!
Did anyone found a way to use bindings for Value Converter Parameters? It's really weird even the official documentation does not specify a solution to achieve this :( I'm probably using the worst solution around by implementing it in a value converter (passing the entire View Model as the input and handling it inside the Value Converter).
Isn't it described in detail in the Docs here? docs.microsoft.com/xamarin/xamarin-forms/app-fundamentals/data-binding/converters#binding-converter-parameters
@@jfversluis thanks, unfortunately it just demonstrates binding to a static value of 255 I was talking about binding to a property or etc. The same part of video that failed. Looks like there is no way.
@@jfversluis I create a new property that simply performs the logic in the getter and then i bind it in XAML. It's a cheating but i prefer creating a new property than creating ValuConverters.
@@rajeshjha3681 That is one way to get around it for sure :) I don't know I feel my ViewModel is then getting cluttered with things it shouldn't be doing. But that's mostly personal preference. I hope my next video will be better for you! :D
O no! Demoes going wrong... What is your worst demo fail?
Truth! Thanks Jony!
thank you gerald for making xamarin so easy to understand...
So nice of you to say Florent! Really appreciate it!
Awesome video, man. I like your style of explaining. Very easy to follow. 👍
Glad you liked it! Let me know if there is something you need!
Did you find out how to bind the ConverterParameter?
Unfortunately it's just not possible. You will want to use MultiBinding: github.com/xamarin/Xamarin.Forms/issues/4565
Very Useful....now make a video about Creating Plugins from Scratch and Custom View Controls using SkiaSharp.
They're on the list, thank you for your suggestions!
Hello Gerald, is there any workaround regarding binding the converter parameter? I'm stuck there too :(
Why should there be a workaround for it? What is not working?
@@jfversluis Hey, he probably meant this part: 15:00 ConverterParameter with Binding (Doesn't Work! Epic Fail 🤦♂)
Is it bad if i use only code behind in my application instead of MVVM? I find code behind very easy.
Absolutely not. Whatever works for you, keep doing that! There is no MVVM police that will come get you. Choosing MVVM will give you some advantages but if you decide you can live without that, that is fine too!
Did anyone found a way to use bindings for Value Converter Parameters? It's really weird even the official documentation does not specify a solution to achieve this :( I'm probably using the worst solution around by implementing it in a value converter (passing the entire View Model as the input and handling it inside the Value Converter).
Isn't it described in detail in the Docs here? docs.microsoft.com/xamarin/xamarin-forms/app-fundamentals/data-binding/converters#binding-converter-parameters
@@jfversluis thanks, unfortunately it just demonstrates binding to a static value of 255 I was talking about binding to a property or etc. The same part of video that failed. Looks like there is no way.
Another way would be to create your own converter and add an additional (bindable) property?
@@jfversluis actually it's a good idea. Thanks alot.
ValueConverters are one of the things i hate about XAML. I always avoid using it.
O no Rajesh! Sorry to bring up traumas! Why do you hate them so much? And what do you do to avoid them?
@@jfversluis I create a new property that simply performs the logic in the getter and then i bind it in XAML. It's a cheating but i prefer creating a new property than creating ValuConverters.
@@rajeshjha3681 That is one way to get around it for sure :) I don't know I feel my ViewModel is then getting cluttered with things it shouldn't be doing. But that's mostly personal preference.
I hope my next video will be better for you! :D