Describe the bug
Very often binding requires a small, rather trivial, function... So trivial that if it weren't needed in XAML it would just be inline code.
Converters exist to bridge this gap, but using a full converter instance can be unnecessarily heavy when using x:Bind, which allows function binding.
My proposal is to introduce public static methods that provide the actual, strongly-type, conversion function into all of the toolkit converters.
Steps to reproduce
Expected behavior
This:
<Resources>
<convert:BoolNegationConverter x:Key="BoolNegationConverter"/>
</Resources>
...
<ToggleSwitch Value="{x:Bind MyValue, Converter={StaticResource BoolNegationConverter} Mode=OneWay}">
Could be replaced with this:
<ToggleSwitch Value="{x:Bind convert:BoolNegationConverter.Convert(MyValue), Mode=OneWay}">
Screenshots
No response
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
BindBack will not be usable because it does not return an actual value and is basically just a function that runs when the dependency property is updated.
Help us help you
Yes, I'd like to be assigned to work on this item.
Describe the bug
Very often binding requires a small, rather trivial, function... So trivial that if it weren't needed in XAML it would just be inline code.
Converters exist to bridge this gap, but using a full converter instance can be unnecessarily heavy when using x:Bind, which allows function binding.
My proposal is to introduce public static methods that provide the actual, strongly-type, conversion function into all of the toolkit converters.
Steps to reproduce
Expected behavior
This:
Could be replaced with this:
Screenshots
No response
Code Platform
Windows Build Number
Other Windows Build number
No response
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
BindBack will not be usable because it does not return an actual value and is basically just a function that runs when the dependency property is updated.
Help us help you
Yes, I'd like to be assigned to work on this item.