User | Kudos |
---|---|
10 | |
6 | |
6 | |
5 | |
4 |
The array "Startup/Always Included" carries these Vi's into pre/post build action VI's.
The order of the vi's in this array depends on the order they have been added to/created in the project when, not the order they can be seen on the project window itself.
Here's the project window:
Here's the order within prebuild vi:
The order is NOT the same. "startup" is the first but if you delete from the project and then re-add it, it will become the last.
I suggest that the order in pre/post build VI should be:
first - startup.vi
following: always included vi's in the same order they appear in the project window.
Also, the always included list should have a 'mechanism' to change the order of the vi's in the list - be it up/down arrow buttons on the side that would move the selected vi or a similar command in a "right click" drop down menu.
In this way, any pre/post build action that may involve any of these vi's can be clearly defined and remain stable during the lifetime of the project without running into the risk of getting the wrong vi to "work" on or having to edit the pre/post build vi to add or edit the vi's names every time there is a change in the startup/always included list.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.