Open michael-hawker opened 3 years ago
I can see the usefulness in what you ask... quite honestly, the whole code on the XamlBehaviors are still legacy from a time where we only had legacy Bindings (instead of compiled ones) and had to resort a lot to reflection, but nowadays that is not the case anymore... makes me wonder if a deeper rethink of this whole thing should be done for WinUI 3 support!
It'd be nice for
CallMethodAction
to support an additional property forMethodParameter
in order to allow overwriting the incoming parameter from the parent behavior to something specified by the developer in XAML:This would provide a little bit more flexibility.