Graph Cursor X position BUG?

[ceties]

Hi, can you somebody verify if what I observe is a bug or just my misunderstanding?

I have used the Cursor.PosX in LV 2009/2010 with no problems but now for some reason this property behaves as Cursor.Index.

The thing I try to achieve is to "bring to center" the cursor. Instead of trying to find the closest x coordinate in the data it represents the passed number as index of a point to which it snaps.... It is not expected behaviour in my eyes and it is not how it worked in previous versions.

Attached is an example demonstrating the problem. 

Thanks 

[mikeporter]

Actually, it looks like it is doing exactly what the help says it should be doing, to wit:

   "Position:X is in the coordinate system of the X Scale value that is associated with the cursor or plot."

That statement from the help is talking about coordinate systems not values, hence it is behaving as it should. One reason I can think of why it might appear that the behavior has changed is the multiplier value. If in your previous work you always had a multiplier of 1, then the index would be equal to the value.

Mike...

[ceties]

Hi Mike,

It behaved in a different way before. No changes in Multiplier. I actually disagree about the statement. It would talk aboun an index but it talks about value instead. And then now CursoXPos ans CursorIndex behave the same, don't they? Is that expected?

[ceties]

When you read the XPos and increment the value by one it should move the cursor 

a) to the expected coordinate (or the closest one) - if it worked as it used to

b) move it to the next point - if it was representing the value as index

None of above happens. It reads it as (a) and writes it as (b). It is a BUG

[Ardent]

Hi Ceties,

this bug in 2011 has been reported and filed in fall 2011, it should be fixed in upcoming version of LabVIEW.