How to add a cursor to a waveform graph on mouse click

[Ty Berry]

Hi, I have a waveform graph which is displaying data. I would like to be able to click on a point on that graph during runtime and add a cursor at that point. Any suggestions? I have been trying to figure this out for a while but I'm completely stuck. Thanks a lot, Ty

[aeastet]

How many samples are you expecting to have on this graph?

How big of a graph are you thinking you are going to need?

How good of resolution do you need for placing this cursor?

[smercurio_fc]

Which part are you having problems with?  Adding a cursor, or positioning it? Have you taken a look at the "Programmatically Control Cursors" example that ships with LabVIEW? That shows you that you basically have to manipulate the Cursor List property.

[Darin.K]

Here is an example of clicking to add cursors to an XY graph.

http://forums.ni.com/t5/LabVIEW/How-to-select-a-set-of-points-in-a-xy-graph-contained-in-an-area/m-p...

[aeastet]

Here is an example that I made to do exactly what I think you want.

[Ty Berry]

Hi Tim, I only have LabView 8.5... I'm not sure how to open the file. I would really like to see it; is there any way you could save it in a version so that I can open it? I'm not totally sure how that would work, but if you can, it would be much appreciated! Thanks, Ty

[aeastet · Accepted solution]

Here is an 8.0 version

[Ty Berry]

Perfect! Thanks so much Tim. That is exactly what I needed.

[RavensFan]

Then please mark Tim's message as the solution to your question rather than your own thank you message.  If you go to the options menu to the upper right of your message, you'll be able to unmark your message as the solution.  Then you can go to his message and properly mark it as the solution.

[Ty Berry]

I did try to do that but (clearly) clicked the wrong message by accident. I tried to un-do it but when I click on the "options" link it just takes me to the top of the page rather than opening the options menu... I'll try again with a different browser though! (using Firefox at the moment... is this a known issue?)

Edit: There we go! Worked on Safari. Thanks again Tim!