property node incorrectly placing cursor

[altenbach]

Here is is fully reproducible under 8.5.1 if I do the following:

• Copy the current code (except for the graph and property node) to a new VI.
• Create a new xy graph, create a cursor
• hook it up
• create a new property node, duplicating the previous one.

The cursor will end up to the left of the minimum as before.

The attached exploratory VI shows some other weird behavior. For example, once the cursor is moved to the real minimum, it stays there.

If the cursor is off-peak and we read the cursorX after just writing it in the same property node, the numbers are different!

More instructions on the front panel.

I really think there is a bug in the code and it should be easy to find since it is reproducible.

[parthabe]

Hi Jim,

I tried to open your VI; but it says like this.

Please see the attached screenshot.

[altenbach]

---

parthabe wrote:
I tried to open your VI; but it says like this.

---

Clear your browser cache and download it once more. Seems you got a corrupt download. The posted file is fine.

[parthabe]

Yeah, it worked.

Seems like some overnight voodoo was sitting inside my PC.

[lmtis]

Hi Brian,

As a test I saved the data to a txt file, rebooted my PC and re-created the VI from scratch.  I still got the same behavior.

[Brinoceros]

Hi all - Thanks for the input! I'll see what I can figure out. 

In the mean time, it looks like altenbach's work-around is the way to go to avoid this (as if I needed to say that)

[Brinoceros]

Looks like we do have a bug here.  And here's your CAR..

This was reported to R&D (#119407) for further investigation.  The accepted work-around for this issue is to write to the Cursor.Index property instead (as altenbach suggested).

As always, we appreciate the feedback!

[X.]

Still not fixed four years later... Do I start to see a pattern of procrastination here?

[Tarek]

X,

According to the CAR, it seems that this bug has been fixed in LabVIEW 2011.

In case you have an earlier version, a workaround would be changing Cursor.PosX to Cursor.Index.

[X.]

I am using LV 2012 latest patch. If you use PosX with a cursor locked to a specific plot, the cursor goes to a random location AROUND the specified position, but never to that position (even though the plot does have a point at that location).

I spent an hour yesterday converting my code to use Cursor.Index and let me tell you: I was not happy.

Moreover, this requires pulling off the plot itself to figure out which index to use, which is

- unwieldy for large plots

- inconvenient when the code should be plot agnostic