LabVIEW
Application builder - Best practice multiple applications from the same main VI
Solved!
@Tonybj The downside is having to find the correct control among the "control reference"-array but its solvable.
You can view the controls order by selecting Edit >> Set Tabbing Order, much like how you can rearrange items in a cluster. Then the controls will be ordered in the array the same as the tabbing order. But this is also the reason my example specifically looked at the control's label. You can iterate over all controls until you find the one where the label matches.
Either way, glad you got it working. Pre- and Post- build VIs can be useful, but you should also document in the Main.vi that the specific controls/indicators will be affected by the build spec. It's hidden code when looking at the Main.vi that can be a real pain for a future developer to inherit, and there's also no easy way of testing both modes while in development mode. This is the primary reason that other people have commented on this post to use .ini files or read the name of the Application at run-time. All the logic is contained. But like all tools, there's a time and place for them.
