Switch Chart logarimic on and off will have problem when you set axis Minimum and Maximum Values

Hi There,

There is problem for switching between logarithmic axis and regular axis, if you set the axis Minimum and Maximum values.

On your sample for file LogarithmicAxisDemo.xml, if we change the Y-Axis to the following:

<ms:Chart.YAxis>
        <ms:ChartAxis Title="Y axis" Style="{StaticResource AxisStyle}" Maximum="1.0e5" Minimum="1.0e2"/>
</ms:Chart.YAxis>

Run the application, click on checkbox a few times, then the curve is gone, because both Y-Axis Minimum and Maximum value is set to be 100000. See attached file.

Could you please fix them? We are using version 6.0, April 10, 2014's nightly builds.

Hello Gordon

Thanks for pointing this out. This issue will be resolved in the next nightly build.

-Jason Fauchelle

Hi Jason,

May 01, 2014's nightly build does not work, the Y axis will have extra tick mark between 100 and 1000. See attached image.

If I set MajorTickSpacing="1000" for Y-Axis before I switch it to Logarithmic, the plot looked nice, but after using logarithmic converter, I want to keep it as 1, 10, 100, 1000, 10000,... (power of 10) on the y-axis tick label, and it will ignore automatically the MajorTickSpacing I set earlier. (of course after I switch back to normal axis, I need to the MajorTickSpacing is in effective).

If the base =2, I need it to be the power of 2 on the tick label, i.e. 2, 4, 8,16 Is that possible at all? Maybe set a property in your Logarithmic converter (bool AutomaticTickSpacing)?

Gordon

Hello Gordon

Great suggestion, I've noted this done as a convenient improvement to the log axis converter. In the mean time, you can get the behavior that you want by setting the MajorTickSpacing property to 1 when using a log axis. This will work for any log base.

-Jason Fauchelle

Thanks, Jason.

Is this new feature on "convenient improvement to the log axis converter" will be available soon or need to wait for next version?

Thanks, Gordon

Hello Gordon

It will most likely be added in a nightly build after the next version is released. Unfortunately tasks that have work-arounds such as this one have lower priority so that we can first resolve bugs or highly requested features.

-Jason Fauchelle