Your comments

Yes, this is a good idea. Glad to see you using the "Place VI Contents" feature.

Does anyone know how to display RTF files on a LabVIEW front panel in a cross-platform way?

I think the definition of a dependency in the context of VIPM needs to be defined. Would this be VIs that:

  • Live outside of the source folder
  • Live beneath LabVIEW
  • Live in other installed packages
  • All of the above

I merged another Idea with this one. Looks like the comment (from Mark Garnett) got lost so here it is:


"There are some times where I want to modify every VI in a package programmatically before building. One example programmatically adding information to the VI description. I can do this with pre-build actions, because I get a list of the source files. Then I can open VI references, modify, save. However, I don't really want  to touch my source code, just what ends up in the package. 

It would be great If we could get paths to temporary files created during the build process-- I could then modify these temporary files and the changes would end up in the built package without munging the source code."

"It would be nice if this could be auto-configured but only when creating new packages (so there are no surprises when opening an existing package)."


Can you explain this some more?

Here is one implementation scenario:

  • Have a global setting under Tools>Options: "Default exclusion filter for new packages:<insert regular expression here>. Then when you create a new package build spec, VIPM would copy the exclusions filter to the new spec and apply it.
  • Now each package build spec would have a copy of the exclusion filter. You could go in and edit this exclusion filter for the spec and change it (if you want), to be different and then re-save it.

You have no objections to VIPM autosaving your project? I have concerns that VIPM should not save automatically. But instead the end-user should perform the save.

Is this basically a request for NOT autosaving? Just want to clarify.

Dependencies are typically installed from the bottom-up by VIPM. Lower-level dependencies are installed first. However you do not have full control over this ordering.