Express VI configuration options

[Yamaeda]

It'd be nice if there were some general options in the Tolls --> Options... menu to configure how Express VI's should behave when dropped. Now there's only "Configure directly", but i'd like 2 more:
1. Show as icon
2. Show Caption
(there might be more, but those 2 is of the top of my head)
It seems i always need to R-click and View as icon and turn off Caption. It'd be nice if that was automatic.
(I'm currently upgrading code that was originally done in some old LV and last in LV2011, so the suggestions are e.g. to replace Open file to File Dialogs, thus this thought)
/Y

[Yamaeda]

*Tools --> Options... 🙂

[AristosQueue (NI)]

No further work is being done to enhance Express VIs in the current platform. Configuration of nodes has been completely reworked in LabVIEW NXG.

[Darren]

National Instruments will not be implementing this idea. See the idea discussion thread for more information.

[Yamaeda]

Fair enough. I do hope that idea is implemented/transferred to NXG then. 😉

/Y

[AristosQueue (NI)]

Yamaeda: In NXG, there is no differentiation between different types of configurable nodes, so there is no halo on any node: a Simulate Signal and an In Range And Coerce node would both be configured using the same right-rail properties pane when the node is selected (and supporting multi-select where overlap exists). Configuration for the concept of polymorphism and operator overloading, when those cannot be computed simply from wires on the diagram, are also blended under that rubric, as they are all basically different ways of configuring a node. The visibility of label/caption is handled entirely differently on the diagram.

Essentially, the entire concept of "node" has been re-thought, taking into account 30+ years of LabVIEW evolution.

[littlesphaeroid]

Though declined, I'll point out that this is especial annoying when including express VIs in packed libraries:

[AristosQueue (NI)]

It seems very strange to me to even attempt to distribute an express VI in a packed project library. Why would you use a binary file to distribute source code? It can't possibly be to protect your IP -- the express VI instances can be converted to real functions to reveal the underlying implementation. What's the goal?

I don't own either feature (PPLs or express VIs), but, personally, that's an extreme corner case that I would never have even thought to test. I'm surprised it works at all.

[littlesphaeroid]

It doesn't work. At all. So the point is moot. It isn't (wasn't?) entirely clear to me that an express VI is source code. It was an ill-conceived notion.

[AristosQueue (NI)]

Glad to have clarification on that. Thanks.