I know the events for indeterminate state transitions are different, but in
the databinding you just get to specify the property you want to bind to and
the trigger mechanism for updating the source. Unfortunately you can't
specify the event to do the update unless you add your own event handler and
use the manual method to call updatesource. It appears that the trigger
mechanism doesn't recognize transitions to indeterminate, only to checked or
unchecked.
"John Bundy" wrote:
Quote:
> haven't tried it as you have below, but i tried to check this intuitively
> with a checkchanged event updating a label.
> Me.Label1.Text = Me.CheckBox1.CheckState
> i found that the indeterminate value did not fire an event with then
> CheckBox1_CheckedChanged event, it did work with CheckBox1_CheckStateChanged.
> So you might try checking against that event instead
> --
> -John
> Please rate when your question is answered to help us and others know what
> is helpful.
>
>
> "dave" wrote:
> Quote:
> > I am binding a 3-state checkbox to an XElement:
> >
> > <CheckBox Content="Summary" IsChecked="{Binding
> > Path=Element[StatusSummary].Value, Mode=TwoWay,
> > UpdateSourceTrigger=PropertyChanged}" IsThreeState="True" IsEnabled="False"
> > Margin="0,79,0,0"/>
> >
> > it properly reports True and False when it is checked or unchecked. but it
> > retains the previous value when in the intermediate state. it would seem to
> > not be firing the propertychanged event to update the xelement when
> > transitioning to the indeterminate state. Is there a way to bind to get back
> > the null for indeterminate?