Search the Community
Showing results for tags 'package builder'.
I'm trying to move my palette location to the Instrument Drivers when building a new package. But once I click on the "Browse for Functions Palette Path" the dialog comes up and never gets past "Populating..." I've tried waiting a good 10-15 minutes and it's still stuck on there, I tried running as administrator and that makes no difference. Am I being too impatient, do I need to wait half an hour or something, or should it populate fairly quickly? EDIT: I've waited over an hour now, and still no luck.
Cross posted on LavaG, but was not getting any replies. So lets try here. I am using the newest version (2020.1) of VIPM, but I had this same issue with the release of 2020. For two of the packages that I have created for internal repos, VIPM has decided that I need a System Package. The posts I have seem from JKI indicate that this is a sub-package that is used internally to the main package, and should be automatically included. However, after I am seeing issues on any PC other than the PC where the package was built. Is there a setting I am missing? Showing the (System) package as a dependency: Package Configuration in the VI Package Configuration Editor Package installed, on the PC where the package was initially created (no issues, no exclamation mark) Package when installed on another PC (NOTICE: the System Package name has changed and there is a red exclamation mark, but there are no errors shown on install of the package).