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, Axis's ActualMin/Max get changed after add and remove data series in the Chart. It happened on the nightly build from Mar 5, 2014 Version 6.0. And It was working on Feb. 24, 2014 nightly build. Here is the step on how to reproduce it: 1) Have a plot that has a Scatter Series or Line Series (or other any data series) 2) Zoom the plot so it is only show part of the curves/points, at this time the ActualMin/Max were changed (not the same as Minimum/Maximum) 3) try to remove the data series from the chart but without changing the axis' ActualMin/Max value 4) Add the same data series back to the chart, again without setting any of the ActualMin/Max or Minimum/Maximum values 5) the plot will zoom back to 100%, and ActualMin/Max is the same as Minimum/Maximum, this is not what we want, and we still want to have the same zooming level as in step 2). This new unwanted behavior may due to the changes you made for related thread "Axis Min/Max and ActualMin/Max value confusing" Could you fix them? Thanks, Gordon |
|
|
|
|
Hello Gordon Unfortunately this is the expected behavior. What you saw before Feb 24th sounds like a bug, and was fixed through that other thread. When series are added to the chart, the data is analysed, and the minimum/maximum range of each associated axis is automatically calculated/updated. By default, setting the minimum and maximum values causes the ActualMinimum and ActualMaximum values to be updated (as discussed in that other thread), causing the chart to be zoomed to 100%. If we did not do this, then loading a series initially would not display the chart because it would remain at 0% zoom. It is difficult for the Chart to determine in each scenario if the developer intends for the Chart to update the axis values automatically, or leave it as it is. We did anticipate this issue and pondered on it for a while, but in the end we decided for the chart to always set ActualMinimum and ActualMaximum when the Minimum and Maximum properties change and leave it up to the developer to control the values if they need to. I assure you that if we start putting in some "smart" logic that guesses what you want in certain scenarios, it will get some of your other scenarios wrong. I personally would like for the Chart controls to be smarter at guessing what to do with the axes in these scenarios, but it is too much of a delicate operation which could inadvertently cause behavior bugs (some of which could go undetected) in your software. What you want to do is set bindings on the ActualMinimum and ActualMaximum properties so that you can have full control of setting them to what you want in this kind of scenario. -Jason Fauchelle |
|
|
|
