Strategies for locking down a Waveform Graph or a Waveform Chart???

[tarheel_hax0r]

> However, I believe it is more convenient to use the paint tool on the front panel

Okay, this is really weird: I tried to tell a Color Box to be the "Transparent" color, but instead of being transparent, it simply mimics the behavior of the transparent "icon" in the color tool - it paints itself white, with a "T" in the middle.

Is there a way to tell a Color Box to be transparent? Or is it forbidden for some reason?

[By the way, I was able to get Front Panel "Decorations" to be transparent, but I'd rather use Color Boxes, since they also appear on the Block Diagram.]

[tarheel_hax0r]

I tried using "Editable", and while it does prevent left clicks, it doesn't prevent right clicks [which still gives the end-user the ability to "Autoscale X", "Autoscale Y", etc.]

[tarheel_hax0r]

The attached VI uses a transparent decoration to cover the Waveform Chart.

[altenbach]

Transparent object are really a pain when editing a VI. I would suggest a slight modification to your second approach:

Instead of the plain event "Mouse Down", use the filtering event "Mouse Down?" and wire a "True" to the discard terminal.

Voila! All mouse event on the temperature graph are ignored completely. 🙂

[tarheel_hax0r]

Thanks! I think the combination of "Mouse Down?" and "Discard?" was just about exactly what I was looking for.

See the attached VI.

[chilly_charly]

Caroline solution seems to be the most efficient solution, sinec it does exactly what you asked for. Just prevent prevent right clicks by disabling run-time short-cut menus (vi properties>window appearance>customize).

CC

[tarheel_hax0r]

Thanks! That's another excellent approach.

I've attached a sample VI.

[DougWilson]

You can't turn the "Value" portion of a Color Box transparent, without showing the "T" for the obvious reason that it needs to show you its current color.
Use a Classic boolean and set BG and FG to transparnet instead, if you really want the item to show up on the BD.

Also a comment on the suggestion that you filter the event.
While altenbach is correct that these is "easier" for the programmer, the suggestion leads to a very bad programming practice from a GUI standpoint. The user is allowed to click on something, but is given no indication why the click is ignored. This would be okay if the object were not something a user would normally be able to click on but in this case, the GUI is sending mixed signals to the user. With the transparent object approaches, especially using a decoration, LabVIEW changes the cursor in a way that provides cueing to the user that the action is not valid.