I have a case with XamNumericRangeSlider and four thumbs, They are all added in XAML. I have binded slider MinValue and MaxValue to a properties in my ViewModel. The binding seems to break the thumbs. I have hard-coded the thumb values for testing purposes and they work fine if I hard-code also my MinValue and MaxValue. But now that I have them binded to ViewModel, all the thumbs are created to value 0.
Are there some rules that need to be followed that I don't know. I'm using the latest 11.2 version of the slider.
P.S. There is no help documentation available for the version 11.2? When it's coming?
Hello anttisimonen,
The ling for online documentation can be found here - http://help.infragistics.com/Doc/Silverlight/2011.2/CLR4.0/?page=NetAdvantage_Silverlight.html.
About slider - XamNumericRange and XamNumeric sliders have MinValue and MaxValue set to 0 and 100 by default. If you want to bind thumbs values you should be aware that when the value of the thumb is out of the range between MinValue and MaxValue, it won't be correct and will be assigned the value of the MinValue of the slider. You should make sure that MinValue and MaxValue are initilised before the Value of all thumbs, in order everything to be handled correctly by the slider.
Please respond if that is answering your question!
Regards,
Nikola.
I suspected something like this and I have now checked that my thumb values are between the min and max values of the slider. The slider itself takes the bindings nicely but the thumbs just don't work. If you like, I can try to reproduce this in a smaller sample project for you to investigate?
Hi anttisimonen,
If you could provide such a sample it would be really time saving for us to investigate and find the problem ! Thank you in advance!
Here's a small sample which reproduces the problem I have with thumb bindings. It uses Galasoft MVVMLight framework so you need to add a reference to GalaSoft.MvvmLight.SL4.dll before you can use it. You can get MVVMLight from here (I'm using v3): https://archive.codeplex.com/?p=mvvmlight
Also remember to add references to your assemblies as well (InfragisticsSL4.Controls.Editors.XamSlider.v11.2 + InfragisticsSL4.v11.2)
Hope this helps.
I have been looking into your sample and i managed to reproduce the problem.While testing it I have found out that this behavior is caused by InteractionMode property of the first thumb which is set to Lock value and that way it does not allow other thumbs to move in the right. I have been creating similar sample , where that particular scenario was working. However i have opened bug item for the development department to , but i don't believe they would manage to fix it for for the upcoming SR, because it is targeted for really soon! I will keep you posted on that topic!
How did you get the similar use case working? I really need some kind of solution for this issue. I guess the possible fix didn't make it to the SR.
I have spent some more time on that problem and i think i have found it finally. It seems that the reason about it is because in your sample you are setting the DataContext for the whole user control. The InteractionMode property of the first thumb is set to Lock and it influences the behaviour of the rest thumbs, that should be to the right, because they have larger values. However, in a sample that i am attaching i am using different way to bind the thumbs of the slider, by specifying source for the binding. As i said before that is a bug and i will contact the developer responsible for that, to fix it for you into the January SR! Hope that is useful for you now!
Nikola
I think the biggest problem with my thumbs was that when changing the values, the locked thumbs didn't allow the new values.
I managed to workaround the issue by clearing and generating the thumbs manually every time I need to change them. This solution works ok and is fine for me.
Let me know if you still are going to fix the issue. Maybe generate a new support request by my name? But it's fine for me if you decide not to do anything to this.
Great! I'll try to use your information to see if I can get it also working already. Looking forward to the January SR...