How do I remove the y value from the cursor palette?

[Ben]

Way cool CC!

But you better watch yourself. If you accomplish the impossible to often, someone will make it part of your job description.

Ben

[chilly_charly]

Deep thought Ben !
As you are probably aware, frenchies are not humble people (not like british...;)). We even have a proverb saying that "impossible n'est pas francais" 😄

[daveTW]

Hi all,
to go back to the topic, I can't run the examples in LV 8 (still 8.0.1), because LV removes the reference to the cursor palette and there is no way to create it like Ben described.
So is this done for security reasons (the dumb LV user should not do this) or did it cause too many problems to handle errors while passing wrong values to it?
Or is it a feature, not a bug?
Greets, Dave

[Jason King]

Hi, Dave.  I will  call this a "feature" as the cursor legend was re-written in 8.0 to be based on a tree control rather than an array of clusters as it was previously.  I made the change (so I'm biased), but I feel this cleans up the interface quite a bit and removes a limitation that was present with the array.  If you (or the user) added more cusrors at run-time, you couldn't size the cursor palette to see all the cursors and change the point style, color, etc.  With a tree control, all one needs to do is move the scrollbar and you can access all the cursors that exist for the graph.  Additionally, the existing cursor legend was not sufficient for representing the new type of cursor (multi-plot) introduced for the mixed-signal graph.

The reason you can't currently get a reference to the cursor legend/palette is to protect the user from messing up the graph.  When we made the change to base the cursor legend on the tree control we envisioned the user being able to get a reference to the tree control and customize it at will - being able to add a separate column for displaying deltas or other extra information that isn't built-in to the legend. Unfortunately, we didn't have time to fully think-through all the ways the user could get into trouble (deleting the tree rows that display the actual cursor data, etc) and come up with a strategy for protecting against it.

I can't make predictions as to when functionality as this might be exposed, but it certainly was our intention to allow for this at some point, so hopefully we can follow through in that direction.

J

[daveTW]

Hi Jason,
thanks for the answer, that makes it clear to me.
Greets, Dave

[pter]

Hi,

I just tried above vi in lv 8.6, but it's still a hidden feature. Isn't there a chance for the next version of lv to unhide the reference and simply include a warning in the help file : "beware ..!" It would help me a lot porting my (still lv 7.1.1) vi to the future.

Thanks in advance

Peter

[Jannis]

Hi,

LabView 2011 and still no property access to the Cursor Legend or an event messaging a user interaction. Is there something in the pipeline. Has somebody filed an idea exchange to vote for it?

Regards Jannis