WPF Converters

Commented Issue: DateTimeConverter should support DateTimeOffset [9634]

kentcb — Thu, 11 Apr 2013 18:54:50 GMT

Subject says it all, really. Just adding this work item so I don't forget to do this later.
Comments: It won't make sense to add this to `DateTimeConverter` because the two types have different usage patterns. `DateTimeOffset` doesn't have a `Kind`, and there are two components to a `DateTimeOffset` that one might want to change during conversion: the `DateTime` and the `Offset`. More thought needed.

Closed Issue: DependencyProperty.UnsetValue instead of null [9635]

kentcb — Thu, 11 Apr 2013 18:41:52 GMT

Some converters are returning `null` instead of `DependencyProperty.UnsetValue`. Review and fix.
Comments: I was wrong. The only places I return null are in `IMultiValueConverter.ConvertBack`, which is the right thing to do according to (the documentation)[http://msdn.microsoft.com/en-us/library/system.windows.data.imultivalueconverter.convertback.aspx]: > Return `null` to indicate that the converter cannot perform the conversion or that it does not support conversion in this direction.

Closed Issue: ExpressionConverter not work with multibinding in silverlight [9533]

kentcb — Thu, 11 Apr 2013 18:35:38 GMT

ExpressionConverter implement IMultiValueConverter, which not visible for silverlight. Maybe add ISilverlightMultiValueConverter (identical to IMultiValueConverter) to library and use it as standart IMultiValueConverter?

Comments: A multi-converter is useless without multibindings, which SL does not have.

Reopened Issue: ExpressionConverter not work with multibinding in silverlight [9533]

kentcb — Thu, 11 Apr 2013 18:35:07 GMT

Closed Issue: ExpressionConverter not work with multibinding in silverlight [9533]

kentcb — Thu, 11 Apr 2013 18:34:51 GMT

Closed Issue: Wrong Assert in WideningBinaryNode.Evaluate [9601]

kentcb — Thu, 11 Apr 2013 18:33:25 GMT

I think 
 
Debug.Assert(convertibleLeftNodeValue != null || maxNodeValueType == NodeValueType.String);
Debug.Assert(convertibleRightNodeValue != null || maxNodeValueType == NodeValueType.String);
 
should be
 
Debug.Assert(convertibleLeftNodeValue == null || maxNodeValueType == NodeValueType.String);
Debug.Assert(convertibleRightNodeValue == null || maxNodeValueType == NodeValueType.String);
 
I get this assertion if I use ExpressionConverter Expression="{}{0} != null" in order to set a button to enabled if a item is selected in a list view. The conversion works as expected.

Comments: Fixed this a while back and forgot to close. I added `NodeValueType.ReferenceType` and checked for that.

Created Unassigned: Clean up source NuGet package [9636]

kentcb — Sat, 06 Apr 2013 13:48:35 GMT

The source NuGet package has extraneous crap in it that isn't required - clean it up.

Updated Release: WPF Converters V1.3.1 (Mar 31, 2013)

kentcb — Sun, 31 Mar 2013 19:12:08 GMT

Modernized the code base:

semantic versioning
using NuGet for dependency management
style changes
test suite overhaul
upgraded code base to VS2012
explicit .NET 4.5 support
explicit Silverlight 5.0 support
other fix-ups

Released: WPF Converters V1.3.1 (Mar 31, 2013)

Sun, 31 Mar 2013 19:12:07 GMT

Modernized the code base:

semantic versioning
using NuGet for dependency management
style changes
test suite overhaul
upgraded code base to VS2012
explicit .NET 4.5 support
explicit Silverlight 5.0 support
other fix-ups

Source code checked in, #1797fd24a7e45b2b1c899a27e3edeaf0f155a4c0

Kent Boogaart — Sun, 31 Mar 2013 19:05:22 GMT

Forgot to update dependency in nuspec.

Created Issue: DependencyProperty.UnsetValue instead of null [9635]

kentcb — Sun, 31 Mar 2013 18:49:30 GMT

Some converters are returning `null` instead of `DependencyProperty.UnsetValue`. Review and fix.

Source code checked in, #8a0d7ddb9d2bffcf7ceb1c35494472de2f362948

Kent Boogaart — Sun, 31 Mar 2013 18:44:13 GMT

Bumping version.

Edited Issue: DateTimeConverter should support DateTimeOffset [9634]

kentcb — Sat, 30 Mar 2013 18:44:10 GMT

Subject says it all, really. Just adding this work item so I don't forget to do this later.

Created Issue: DateTimeConverter should support DateTimeOffset [9634]

kentcb — Sat, 30 Mar 2013 18:43:39 GMT

Subject says it all, really.

New Post: Make Control Visible Only if Window Maximized

MichaelTR — Wed, 14 Nov 2012 16:42:49 GMT

I'm trying to collapse a control as long as the parent window is not maximized.

Here is what I have so far (collapsing if ActualHeight < 500) and is working:

<Window x:Class="TestApp.AnalyseWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:wpfconverter="clr-namespace:WpfConverter;assembly=WpfConverter"
        x:Name="thisControl"
        WindowState="Maximized"
        Height="600" Width="800"
        MinHeight="300" MinWidth="300">
    <DockPanel>
        <Label DockPanel.Dock="Bottom" Content="Only show when maximized">
            <Label.Visibility>
                <Binding>
                    <Binding.ElementName>thisControl</Binding.ElementName>
                    <Binding.Path>ActualHeight</Binding.Path>
                    <Binding.Converter>
                        <wpfconverter:ExpressionConverter>
                            <![CDATA[
                            {0}  < 500 ? "Collapsed" : "Visible"
                        ]]>
                        </wpfconverter:ExpressionConverter>
                    </Binding.Converter>
                </Binding>
            </Label.Visibility>
        </Label>
        <Label Content="Show always" />
    </DockPanel>
</Window>

But what I can't get to work is doing something like {0} == "Maximized" ? "Visible" : "Collapsed" on the binding path WindowState.

Can anybody tell me, how to do this on the WindowState of thisControl?

Source code checked in, #69631

Project Collection Service Accounts — Mon, 01 Oct 2012 21:13:48 GMT

Upgrade: New Version of LabDefaultTemplate.xaml. To upgrade your build definitions, please visit the following link: http://go.microsoft.com/fwlink/?LinkId=254563

Source code checked in, #69630

Project Collection Service Accounts — Mon, 01 Oct 2012 21:07:03 GMT

Checked in by server upgrade

Created Issue: Add a simple boolean inverter? [9633]

HolySamosa — Tue, 11 Sep 2012 00:35:05 GMT

How about adding a simple boolean inverter? It's trival and most of us have probably implemented our own, but now that I'm using a converter from WPF Converters it would be great to drop my own implementation. (Perhaps the Expression Converter can handle this, but I wonder if the there would still be a place for a bool converter sue to ease of use?)

New Post: ExpressionConverter support string comparison?

kentcb — Mon, 03 Sep 2012 09:37:22 GMT

This is a supported scenario, but there are several syntactic problems with your code. Unfortunately, embedding expressions in XAML can be a bit of a nightmare, so it's often best to just place it inside a CDATA section:

    <Button>
        <Button.IsEnabled>
            <Binding>
                <Binding.Converter>
                    <con:ExpressionConverter>
                        <![CDATA[
                        {0} == "Custom"
                        ]]>
                    </con:ExpressionConverter>
                </Binding.Converter>
            </Binding>
        </Button.IsEnabled>
    </Button>

Of course, if you need this more than once (or even if you just prefer this aesthetically) you can define the converter as a resource and reference it from your binding:

    <Window.Resources>
        <con:ExpressionConverter x:Key="IsCustomConverter">
            <![CDATA[
            {0} == "Custom"
            ]]>
        </con:ExpressionConverter>
    </Window.Resources>
    
    <Button IsEnabled="{Binding Converter={StaticResource IsCustomConverter}}"/>

HTH,
Kent

New Post: ExpressionConverter support string comparison?

brinko99 — Tue, 28 Aug 2012 21:18:54 GMT

I was hoping to use the ExpressionConverter to perform a string comparison:

IsEnabled="{Binding Path=, Converter={con:ExpressionConverter {}{0}=='Custom'}}"

This does't work and gives the error: The argument name is missing. Can ExpressionConverter be used in some fashion like this? If not, might this be considered for a future release?

I found a workaround using the MapConverter as such:

<MenuItem.IsEnabled>
    <Binding>
        <Binding.Converter>
            <con:MapConverter>
                <con:Mapping From="Required">
                    <con:Mapping.To>
                        <System:Boolean>False</System:Boolean>
                    </con:Mapping.To>
                </con:Mapping>
                <con:Mapping From="Custom">
                    <con:Mapping.To>
                        <System:Boolean>True</System:Boolean>
                    </con:Mapping.To>
                </con:Mapping>
            </con:MapConverter>
        </Binding.Converter>
    </Binding>
</MenuItem.IsEnabled>

Thanks.