Static VI reference should be sufficient to cause executable builder to include VI's front panel

[SpaceX Trip]

If you try to build an executable of a VI that only uses a static VI reference to call a subVI - you must either select

1. "show FP on call" in the referenced subVI

OR

2. you must include a property node or reference on the block diagram of the referenced subVI

I believe "always including" the subVI in the build spec works as well.

Failing to do so apparently results in the builder to NOT include the called vi's front panel with the build, resulting in the subVI failing to function in the executable environment.

While that all makes "sense" - it is unintuitive and the workarounds are not ideal.

The application builder should look at static VI references when looking at the build and automatically include the referenced VIs in the build.

[tst]

Are you sure you're talking about including the VI, as opposed to including the front panel?

The reason I'm asking is that I don't see why creating a property node in the VI would cause the VI itself to be included if it wasn't already included before, and because as far as I can remember, static subVIs I had in the past always were included in the build (although I admit that they almost certainly had a property node on the BD so that their FP would be included).

If this does cause it to be included, I would argue that not being included in the other case is a bug.

In any case, there is also a counter-argument: Sometimes you would only use the static reference to get the connector pane pattern for the subVI, so that you can run it using the CBR node. For those instances, you might not want the VI and all of its hierarchy, but I would agree that these cases are probably rarer.

[SteenSchmidt]

Static VIs are included in the build, but their front panels may or may not be included, exactly as you describe. This is intended behavior and shouldn't be changed. Often the FP isn't used, so it of course shouldn't be included by default. Cheers, Steen

[AristosQueue (NI)]

tst: It isn't just any property node that makes the panel be included. It is any *statically linked* property node to something on the front panel that makes the front panel be included. Also, any statically linked control reference node.

[tst]

Yes, I'm aware of the distinction, but the idea talks about the VI itself not being included, which doesn't sound right.