[Bug Report] Graph "Copy Data" Method Doesn't display free cursors correctly

[X.]

Here is an annoying bug in the "Copy Data" method of Graphs.

As illustrated in the picture below (FP of the attached VI), two identical XY Graphs with identically positioned cursors:

result in completely different results when the right-click menu "Copy Data" method is used, and the result pasted in your favorite Microsoft Word editor:

versus:

A potential workaround is of course to not use free cursors, but that is not always an option.

Tested in LabvIEW 2015 SP1 64 bits (Windows 7)

[billko]

I'm curious - do you ever actually use LabVIEW?  😄

[X.]

What's that supposed to mean?

As in "I find so many issues with it and file reports that I can't possibly find time to do any work with it?"

I would understand you asking that very same question to NI developers...

[billko]

---

@X. wrote:

What's that supposed to mean?

As in "I find so many issues with it and file reports that I can't possibly find time to do any work with it?"

I would understand you asking that very same question to NI developers...

---

It was mostly because of this thread coming hard and fast on the heels of the last post related to graphs.  You don't actually post very often, so I'm guessing that in between, you are actually coding.

[WestOfEden]

Thanks for bringing this to our attention. Does this happen when copying any graph where you're using free cursors? 

[mikeporter]

What data exactly are you copying? I don't see any data. If you want an image of the graph, there are methods for that which you should be using.

Does the same thing happen with pasting into other locations? LibreOffice? AbiWord? Have you tried different versions of Word? How about Office 365? In other words this might not be a LabVIEW problem at all.

Mike...

[X.]

@WestofEden: I have done all the above and provided a barebone example to show how simple the problem is to see.

Of course adding a plot doesn't change anything to the provlem. How do you think I found out about this problem in the first place?

[WestOfEden]

I understand, thank you for providing us with that. In searching to see if this was reported previously, I found that there is currently an open service request in regards to the issue. I assume it was you that created it, since it did reference this post. Since there is a request open for the issue, that applications engineer will continue working on validating the issue right now.

If that is not your request, please let me know and I'll keep an eye on it and pass along any developments.

[X.]

I did submit this bug report to NI indeed. This is what I usually do after I get some feedback (constructive or otherwise) from other users, in case I missed something obvious.

I will report the CAR number if one is issued.

[X.]

CAR 597373 was filed for this problem.