12-03-2011, 09:41 AM
First I want to thank you for your excellent programs and I have
had a lot of fun with them.
I am trying out the new version 5.0.1.0 and have found a couple
of problems with the waterfall component in Visual Studio 2008
using VB.
1. I am trying to set custom axis scales. The modes are not clear
since the time and frequency choices need a scaling factor from
array index to be meaningful so I was using auto for MajorTicksMode.
The only way it will accept a YaxisMax value is using a a
Mitov.MaxAxisValue assignment. For YAxisMin it will accept a
Mitov.Plotlab.AxisValue assignment. However, the YAxisMax
assignment has no effect on the displayed scale. It is always
1000. If I look at Waterfall1.YAxis.CurrentMax, it gives the
correct value (if not zoomed). Using the same form on the xaxis
sets the value correctly.
2. The minimum value of the MajorTicks step is 1 when you zoom
in. Further zooms leave you with a blank axis. This appears to
be true for the xaxis as well.
3. I wrote you a year or so ago about a problem with the waterfall
xaxis and it still has much of the problem. It acts like one of the
internal variables is an integer. Any span less than 1 blows up
the display. If you zoom and try to pan, it just zooms back out
or the whole scale disappears depending on the values.
I have a small demo project that shows this effect if that would
be useful.
Thanks again.
had a lot of fun with them.
I am trying out the new version 5.0.1.0 and have found a couple
of problems with the waterfall component in Visual Studio 2008
using VB.
1. I am trying to set custom axis scales. The modes are not clear
since the time and frequency choices need a scaling factor from
array index to be meaningful so I was using auto for MajorTicksMode.
The only way it will accept a YaxisMax value is using a a
Mitov.MaxAxisValue assignment. For YAxisMin it will accept a
Mitov.Plotlab.AxisValue assignment. However, the YAxisMax
assignment has no effect on the displayed scale. It is always
1000. If I look at Waterfall1.YAxis.CurrentMax, it gives the
correct value (if not zoomed). Using the same form on the xaxis
sets the value correctly.
2. The minimum value of the MajorTicks step is 1 when you zoom
in. Further zooms leave you with a blank axis. This appears to
be true for the xaxis as well.
3. I wrote you a year or so ago about a problem with the waterfall
xaxis and it still has much of the problem. It acts like one of the
internal variables is an integer. Any span less than 1 blows up
the display. If you zoom and try to pan, it just zooms back out
or the whole scale disappears depending on the values.
I have a small demo project that shows this effect if that would
be useful.
Thanks again.