Creating an illuminated flowpath on the front panel

[paul_a_cardinale]

I found them while poking around with scripting.

Haven't found much else particularly interesting except for some decorations.

The file "Decos.vi" has the interesting decorations.

The file "Object_Style_Ring.ctl" has the codes for all of the objects I've found.

[Broken_Arrow]

---

@paul_a_cardinale wrote:

I found them while poking around with scripting.

Haven't found much else particularly interesting except for some decorations.

The file "Decos.vi" has the interesting decorations.

The file "Object_Style_Ring.ctl" has the codes for all of the objects I've found.

---

Nice!

You should post an Idea on the Idea Exchange to include the pipes (controls and decorations) as part of the normal palette setup.

[Broken_Arrow]

As I mentioned in an earlier post in this thread, atttached is an example of an illuminated flowpath using decorations, and also uses the UID scripting property node, as mentioned in this Micro-Nugget . It uses the pipes as mentioned above.

You need LV 2011.

[Broken_Arrow]

I have been informed that my VI above is password protected. The password is "starbucks" without the quotes. Sorry about that!

[smi38]

The multi-segment pipe is bugged.

If you set its value with the value property node, the state will be reversed.

Try it.

[Ben]

---

@Callahan wrote:

The multi-segment pipe is bugged.

If you set its value with the value property node, the state will be reversed.

Try it.

---

Please post a sample to illustrate.

Ben

[smi38]

Hello.

Try this VI to see this ugly bug 

[Ben]

When I work with the pipes I seldon use them as booleans but rather drive the colors using the colros property nodes, so...

WHat exactly does not seem right to you?

Ben

[smi38]

grey = false

blue = true

but in mith multi-segment pipe + property node, we have grey=false then grey=true then blue = false

try my VI to see that

I don't care about the colors, my purpose is about the link beetween color and associated value.

[hans17]

Just an FYI that the bug SebastienM found with writing the value of a Multi-Segment Pipe indicator still exists in LabVIEW 2015 and the associated DSC module.  Just ran across it today.  Adding special code to work around this bug by inverting the value before writing it to Multi-Segment Pipe indicators via a property node.

Perhaps NI is leary of fixing this bug for fear of breaking code that has this type of workaround.

Hans