views:

178

answers:

2

Here's a little XAML fragment. You will see

<StackPanel>
            <TextBox x:Name="txtValue">250</TextBox>
            <Slider x:Name="slide" Value="{Binding ElementName=txtValue, Path=Text, Mode=OneWay, UpdateSourceTrigger=PropertyChanged}" Minimum="0" Maximum="500"></Slider>
        </StackPanel>
  1. when you change the textbox value, the slider updates
  2. If you change the slider value explicitly, the previous behavior breaks a.k.a. stops working.

If I remove the Mode=OneWay set directive, (defaults to two-way) everything works perfectly.

Why is this happening?

+3  A: 

Your data binding is not broken but deactivated (http://en.wikipedia.org/wiki/Euphemism):

System.Windows.Data Warning: 75 : BindingExpression (hash=52697953): Deactivate
System.Windows.Data Warning: 99 : BindingExpression (hash=52697953): Replace item at level 0 with {NullDataItem}
System.Windows.Data Warning: 59 : BindingExpression (hash=52697953): Detach

Setting the trace level to high will produce this message in the VS output window in case you move the slider:

<Slider xmlns:trace="clr-namespace:System.Diagnostics;assembly=WindowsBase"
        Value="{Binding trace:PresentationTraceSources.TraceLevel=High,
            ElementName=txtValue, Path=Text, Mode=OneWay,
            UpdateSourceTrigger=PropertyChanged}"
        Minimum="0" Maximum="500"></Slider>
Alex Janzik
Why does it detach? It kind of defeats the purpose of one-way binding if doing something like moving the thumb on the bound control deactivates or unhooks the binding. By broken, I meant the expected behavior isn't seen anymore.
Gishu
That's the way it is implemented :-(If it does not meet your needs don't use WPF data binding.
Alex Janzik
+3  A: 

Use mode=TwoWay and set the UpdateSourceTrigger=Explicit.

h4444
This works...but doesn't explain any of the why.
Beska