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
|
Hi There In the Xaml I use:
In the ViewModel I have following property :
On the run time, I checked the DataContext of the chart even the axis of myY, they are all valid and right (my view model). I even binding the property to the textbox and it works. I cannot find any example to have binding on Axis's Maximum. What did I do wrong here? Please help! Gordon |
|
|
I have to use Mode=TwoWay... as the following
|
|
|
Hello Gordon Sorry for the inconvenience here. The way you are setting things up is probably causing the binding to be set after the chart has already specified that the axis range should be set automatically. By setting the Maximum or Minimum value (either in xaml or with a binding) before the chart is loaded, the chart will disable automatic axis range. Usually this works fine if the property you are binding to is in code-behind or in a view-model that is the DataContext of the window/page. You may be setting up your view model in a scenario that we have overlooked. The chart is being loaded before the binding is in place which causes automatic axis ranges to be enabled, thus overriding your property values. Setting the TwoWay mode like what you have done is the best way to solve this. -Jason |
|
|
Hi Jason, The axis Maximum and Minimum binding still have problem even with TwoWay Binding. You can reproduce this by using the sample project I eamil to you. Here is how to reproduce it:
Is it possible for you to fix the problem? It is really annoying... I used the April 3rd Nightly builds. Thanks Gordon |
|
|
Hello Gordon Thanks for the repro project, this issue has been resolved and will be available through the next nightly build. Jason Fauchelle |
|