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, On version 6.0 if the Axis values are strings, when you setting the Maximum/Minimun values the ActualMin/ActualMax value will not set probably. By default if the axis values is numerical values, the ActualMin/ActualMax of axis is automatically set to the Min/Max value if Min/Max values are set. (Tell me if I am wrong) But for the string values (i.e. "Value 1", "Value 5" "Value 3" "Value 6", if we set the Minimum = "Value 1", and Maximum="Value 6". Then ActualMin = "Value 1" and ActualMax also equal to "Value 1" not "Value 6". This is not always happening. But once it happened, you have to unzoom it to 100% in order to see other data bars in the bar graph. I am using Apri. 24, 2014 nightly build. I spend quite some time to identify the problem. Thanks, Gordon |
|
|
|
|
Hello Gordon There was not much support for setting strings directly to the Minimum and Maximum properties. Mostly just support for numbers and date times. In the next nightly build, the support for setting strings will be much better for you. -Jason Fauchelle |
|
|
|
|
Hi Jason, The same problem exists on April 25, 2014 nightly build. If we set Min/Max of axis, do we have to set Actual Min/Max? If we set ActualMin/Max after setting Min/Max, it works. Thanks, Gordon |
|
|
|
|
Hello Gordon At my end I do not need to set ActualMin/Max, but it is good to hear that setting these value solves the problem for you. -Jason Fauchelle |
|
|
|
|
Is that possible, when the Minimum value get set, it automatically changes the ActualMin when it is string? Thanks, Gordon |
|
|
|
|
Hello Gordon It is doing this already, and is working in all my tests. There are no conditions around the setting, so I'm not yet sure why it would not be working for you. It is probably an issue at our end, but I'll need to work out how to reproduce this first. Could you send a simple repro project, or describe how to modify one of your previous projects to reproduce this issue. It may have something to do with building the chart in code or/and something to do with the order that properties are set or bindings are resolved. -Jason Fauchelle |
|
|
|
|
Hello Jason, On My actual application I can reproduce it every time. I spent big trunk of my time to try to do the same thing on the reproducing project, but no success. I changed my code so in my Actual application works now without calibrated setting the ActualMin/Max. Thanks, Gordon |
|
|
|
|
Hello Gordon Good to hear you found a solution. -Jason Fauchelle |
|
|
|
