Not visible plots taken into account with new option AutoScaleVisibleLoose

[OuaisBla]

Hi guys,

Here's a description of the behaviour with AutoScaleLoose on the WaveformGraph:

7 plots between 0 and 50 (for instance) + 1 plot with greater value like 65536.

So, the Y range goes from 0 to 70000.

If you set not visible the 8th plot, the Y range goes from 0 to 50, which is nice.

But the AutoScaleVisibleLoose behaviour is not the same:

7 plots between 0 and 50 (for instance) + 1 plot with greater value like 65536.

So, the Y range goes from 0 to 70000.

If you set not visible the 8th plot, the Y range still goes from 0 to 70000, which is not what I expected.

Tks,

Jean

[JonathanN]

Hi Jean,

Thanks for reporting the issue as the behavior you are seeing is not correct. We have created a bug report for this incident with ID #113612.

Best Regards,

[JonathanN]

Hi Jean,

I just wanted to let you know that we did fix the problem and it will be included in the next release of Measurement Studio.  As a workaround, you can do the following:

1. Create a second Y axis called invisibleAxis, and set invisibleAxis.Visible to false.
2. Use ShowPlot method to show/hide the plot, instead of just setting plot.Visible to false. See the code snippet below:

private void ShowPlot( WaveformPlot plot, bool visible )
{
    plot.Visible = visible;
    plot.YAxis = (visible ? yAxis1 : invisibleAxis);
}

Best Regards,

[OuaisBla]

Thanks Jonathan,

I'm looking forward to install the next release. Is a date scheduled soon?

A quick question about the AutoScaleVisibleLoose feature: Do you have benchmark performance tests showing comparable performance as the AutoScaleLoose feature for the WaveFormGraph?

I'm wondering because, my system is able to process 800 000 data point (8 plots of 100 000 data each) per second. So far, the WaveFormGraph with the AutoScaleLoose option is able to do it perfectly using good programmation techniques. I have use a little the AutoScaleVisibleLoose option with the feeling that it might have a slight impact on performance compare to the AutoScaleLoose, but nothing out of doubts, just an impression.

Am I wrong to think that the way AutoScaleVisibleLoose compute the min and max values required more slightly more processing than AutoScaleLoose do?

By the way, for the 8.5 release, the EndLabelsAlwaysVisible feature is a nice addition.

Best regards,

Jean