How can I restrict the movement of a grabbed cursor to the visible part of a graph?

[allaba]

When I grab a cursor in a graph and come too close to the left or right boundary of the graph (in a x-direction movement), the displayed graph pans out to the right or left of the graph window. Is there a setting to suppress this or do I have to suppress it programmatically? And if so, how? Wouldn't I need a 'Cursor Move?' filter event.

-Franz

Message Edited by ahlers01 on 02-18-2009 03:57 PM

[PeterAdelhardt]

Hi Franz,

I am not aware of such a filter event. As a workaround you can check the boundaries of the current plot and reset the cursors accordingly. I attached a small demo VI that serves this purpose. 

-Peter

[Ben · Accepted solution]

Is

Right-click >>> Advanced >>> Cursors Scroll Graph

un-checked?

Ben

[altenbach]

There is no code needed! 🙂

Right-click the graph...advanced... and uncheck "cursors scroll graph".

(edit: ahh... Ben's faster again :D)

Message Edited by altenbach on 02-19-2009 07:16 AM

[PeterAdelhardt]

Thanks guys,

I was not aware of this, either. 

-Peter

[Ben]

---

altenbach wrote:

There is no code needed! 🙂

Right-click the graph...advanced... and uncheck "cursors scroll graph".

(edit: ahh... Ben's faster again :D)

Message Edited by altenbach on 02-19-2009 07:16 AM

---

Sorry Christian. Giving credit where it is due, I think it was you that taught me that trick.

[Insert tongue in cheek]

So judging by Peter's posting is looks like all of your (Christian) postings should be required reading for NI AEs.

What do you think?

[Remove tongue from cheek]

Ben

Message Edited by Ben on 02-19-2009 09:24 AM

[altenbach]

In addition (if I remember right), things are also a bit more complicated in ancient LabVIEW versions. If you use a very old version, it is possible to drag the cursor way outside the active window because the cursor keeps mouse focus even if the mouse wanders way past the graph area edge. If you release it outside, it might be difficult to get the cursor back. 😉 Some older LabVIEW versions need some extra code to prevent this from happening.