Control References Node

[DavidBTaylor]

We have an internal tool at Erdos Miller that we've turned into a product. It's a node that outputs a cluster of references to all controls on the front panel. A free trial is available for download here:

http://info.erdosmiller.com/node-control-references-software-download-v1

It replaces code like this:

With a single node:

It also lets you:

• Bind the output type to a typedef.
• Include a reference to the owning VI and/or the owning VI's front panel.
• Exclude references to controls above or to the left of the origin.
• Optionally exclude controls individually.

Controls on tabs are organized into page clusters. Try it out and let us know what you think!

[crabman]

Hi David,

this looks really nice! I just downloaded the trial version, but it seems to be not working. The tool only outputs a numeric value, not a cluster:

I installed the trial version with VIPM and am using LV2017 SP1 (32bit). Did I miss something or is there a bug?

Regards

[GerdW]

Hi crabman,

I got the very same problem for new VIs with just some controls and old VIs from existing projects. I already contacted Erdos Miller (David Taylor).

What happens when you double-click the XNode? (That was the last question of David after I already shut down my computer last night.)

[DavidBTaylor]

crabman,

There appears to be a bug. Others have had the same issue that you are having. I'll let you know as soon as we've figured it out. Thanks for trying it out!

[crabman]

---

What happens when you double-click the XNode? (That was the last question of David after I already shut down

---

I tried double-clicking but it seemed as if nothing happened.

Thanks for your replies guys. I'm really looking forward to the updated version.

[DavidBTaylor]

We've found that this current version only works with English LabVIEW installations. We are working on an update that will be language independent and will post an update when it's done.

[DavidBTaylor]

Language-independent update just landed!

For those curious, the node was creating some property nodes and setting the selected properties by the property's name, which varies from one language to another. We just needed to update it so that they were set by the property's unique ID.