Measurement Studio for .NET Languages

cancel
Showing results for 
Search instead for 
Did you mean: 

Cursor always stays at the left side of the graph

Hello,

I have a scattergraph. The x-axis data range is from 10hz to 800hz. The cursor is initialized to 10hz.  I set the display x range from 20hz to 600hz. Now the cursor is out of sight. Then I manually set the cursor x position to the minimum value of the x-axis which is 20hz. So far so good. However when I start to measurement and take data, the cursor jump back to 10hz where is not in the display range.

It is a little bit annoying because you can't see the cursor even though you know it is there. What is best way to have the cursor stay on the displayed area instead of hiding.

I am using Measurement Studio 8.0.1
Thanks.
0 Kudos
Message 1 of 4
(3,537 Views)
With M.S. 8.0.11.236 and VB .NET 1.1, I did not experience this problem.

> ...when I start to measurement and take data, the cursor jump back

Please review this part of your code.
For debugging purposes you can create an event handler for the event "XYCursor.
PropertyChanged" and find the moment when your code changes the property "XPosition" (e.PropertyName = "XPosition").

0 Kudos
Message 2 of 4
(3,531 Views)
Thanks for your reply. I use this property to check if the XYPosition is changed. It helps me a lot to understand what is going on.

My description in last message " the cursor jumps back to 10Hz" was not quite correct.  The cursor snapmode is set to be "NearestPoint". So when the test starts to take data, the first point is at 10hz(this point is out of display range.), the cursor will find the nearest point which is 10hz even though I set XYPosition to Axis.minimum value before the test starts. The next data point is at 26Hz...

I wonder how to get the cursor in the display area in this situation?
0 Kudos
Message 3 of 4
(3,531 Views)
For example you can:
- check the moment when XYPosition was changed;
- if the cursor is not visible, move the cursor to the data point which is in the display area.

You can also use the mode other than "NearestPoint".
0 Kudos
Message 4 of 4
(3,520 Views)