This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
I'm using a DualSlider and it is giving me a Binding error: System.Windows.Data Error: 5 : Value produced by BindingExpression is not valid for target property.; Value='-16' BindingExpression:Path=; DataItem='Double' (HashCode=-1070596096); target element is 'Border' (Name=''); target property is 'Width' (type 'Double') Here is the DualSlider, there's no Border anywhere in my xaml, and I don't see any Width either. ms:DualSlider AllowOverlap="False" Minimum="0" Maximum="20" Width="200" ToolTip="{Binding MinMaxXString}" ShowTopLeftTickMarks="True" IsInstantMoveEnabled="True" ShowTopLeftLabels="True" LabelStep="2" RangeStart="{Binding VerticalXAxisMin}" RangeEnd="{Binding VerticalXAxisMax}" MinimumRange="1" SnapToTickMarks="{Binding Snap,Mode=TwoWay, NotifyOnSourceUpdated=True, NotifyOnTargetUpdated=True}" Is this a bug or am I doing something wrong? Thanks! |
|
|
|
|
Hello Leah Apologies for the delay. This sounds like a bug at our end. I'll look into this for you first thing next week. -Jason Fauchelle |
|
|
|
|
Hello Leah I have not been able to reproduce this yet. Could you please send me the values of the RangeStart, RangeEnd and SnapToTickMark properties at the time of the binding exception. Also which of our themes are you applying (if any)? -Jason Fauchelle |
|
|
|
|
Hi Jason, I'm not applying any themes. SnapToTickMark = False, RangeStart (bound to VerticalXAxisMin) = 0, RangeStop (bound to VerticalXAxisMax) = 9. Thanks for looking into this! -Leah |
|
|
|
|
Hello Leah Thanks for the values. It looks like this binding exception may not be coming from the DualSlider. I have not been able to reproduce the problem, or find any point in the code that would indicate the problem. Could you please send us a repro project to help us debug this. Or you could comment out bits of your xaml code to deduce what control is causing the exception. If commenting out the DualSlider solves the problem, it may be that something else that binds to the same properties as the dual slider is causing the exception. -Jason Fauchelle |
|
|
|
|
Hi Jason, I will try commenting out bits. I did notice that for a dual slider in the vertical orientation, the startRange is set to the max value and the end range is set to the min value. Is this flipped? |
|
|
|
|
Hello Leah In vertical orientation, the labels were positioned in the reverse order. Could this be what you meant? This bug will be resolved in the next nightly build. Other than that, it is functionally working. By default, the minimum is at the bottom, and the maximum is at the top. If you need to reverse this, you can set IsReversed to True. -Jason Fauchelle |
|
|
|
