Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


hooovahh last won the day on July 18 2017

hooovahh had the most liked content!

Community Reputation

7 Neutral

1 Follower

Recent Profile Visitors

4,292 profile views
  1. I too would be interested in a way to make this work in an automated way. But until then one thing that might help make less steps, is making a VIPC with all the packages you want contained in it. Then on the new machine, after installing all things NI, you can double click that VIPC file, it will open it in VIPM, and ask what version to install them in, and then it installs all the packages at once. It still is a manual process but you don't have to select packages from a list, or be connected to the internet.
  2. I have a build that crashes LabVIEW with an access violation, and then VIPM gets an error. The build is attached. What the problem is, is that in there is a class, and that class is renamed during the build process adding the suffix "_hooovahh". But in that package is also a demo VI named "Defined Slider Test.vi" which uses a property node on that class. I've found that if I build, with the demo VI having a property node, linked to the existing class name, that during the build a rename takes place and crashes LabVIEW. If I disable the rename it builds properly, and if I enable the rename, but remove the property node in the demo VI, it also builds properly. I also found that if I add this demo VI to the class it renames properly which for now is a fine work around. Can this bug be addressed so that VIPM properly builds and renames the class, while not crashing LabVIEW if a property is linked to the class in another VI? Won't Build With Demo and Rename.zip
  3. The period folder is auto generated by VIPM during the build process. This is a temporary location where all files are copied to and processed. During the build this path exists and has the files in it. After the build fails (or finishes) it will cleanup that folder.
  4. Can someone from JKI tell me why this package doesn't build? It is relatively simple with no Pre/Post VIs, no file renaming, only a functions palette. But there are some XNodes and they are going into the vi.lib. On attempting to build it gives the following error: During the build I navigated to those folders and they exist and the files are there. If I remove that one XNode and its support files it builds properly. If I add it back with the support files it fails to build. I've tried mass compiling, resaving, and renaming VIs but it still errors. If I delete all other XNodes, and all other support leaving Common and the Compare to Constant, it also fails to build. Any help is appreciated. EDIT: LabVIEW 2018 SP1 F3 32-bit, VIPM 2018 0.0.f2, Windows 7 x64. XNodes Won't Build.zip
  5. I guess alternatively the Pre/Post VIs could be placed somewhere under the package source, so they are scanned. However for me I use the same Pre/Post VI for multiple packages and it is stored in a folder that isn't shared by any package. Thanks Jim.
  6. If there is a dependency added to a Pre/Post Install/Uninstall VI, this dependency isn't detected by the Scan for Dependencies function. Attached is a package that has a single VI that doesn't do much. But the package has a Pre-Uninstall VI that has a dependency on an OpenG Wait. Scanning for dependencies doesn't find any and I suspect it is because the Pre-Uninstall VI isn't part of the package source. The reason I want this is because my Pre/Post Install/Uninstall VIs are getting large and I wanted to make subVIs but they aren't brought into the package, only the top level. My work around for this is to call subVIs that are already installed. I intended on making a single package that is something like "Package Tools" which all packages that use the Pre/Post VIs will depend on. I can still add this manually but will often forget since all other dependencies are properly found on a scan. Reuse Test.zip
  7. Well I was just able to uninstall and reinstall that package with 2016 32-bit Windows 7 x64. What version of VIPM are you using? I'd expect every version to be compatible with OpenG. Do other packages install alright in 2016?
  8. Update from JKI: This issue is planned to been fixed in VIPM 2018. So I can successfully build packages with VIMs in them. But I found that if I need to make a package, that depends on a package, which contains a VIM, the build will fail. First install the hooovahh_array_vims- package. Then try to build the File IO package, which at the moment only contains one VI. If it is like my setup the build will fail with this error. If I remove the VIM dependency by replacing it with the OpenG one the build is successful. Build Fail VIM Dependency.zip
  9. So on VIPM 2017.0.0f1 I'm having a build that fails if I have some specific VIM, and the Renaming Convention is set. If I don't have renaming, or if I don't include this one VIM then things seem to work properly. Here is the error And attached is the source and build spec. If the Filter 1D Array-VIM.vim is removed from the source, then the build works (renaming all the other files to have _Hooovahh as a suffix). Or if the Filter VIM is left but renaming is disabled the build is successful. Array.zip
  10. The recently posted update VIPM 2017 F1 fixes this issue for me. Finally I can build all the VIM packages I've been wanting to.
  11. I found that if you go to the main download page and enter your email address it will start the download for version 2017 of VIPM. Even though the page still says the version is 2016.
  12. So...is anyone from JKI monitoring these forums? I have a show stopping bug that I posted two weeks ago, in the latest version of VIPM, can anyone give any advice? Thanks.
  13. Update: this issue has been fixed in VIPM 2017f1 I've been using the new VIMs feature of VIPM 2017 and am having some issues getting it to build successfully. If I have a VIM on the palette it builds just fine, but if I add a VI that calls that VIM the build fails, even if that VI isn't on the palette. Attached is a zip with my source. It fails to build because the normal VI "Is Variant Repository.vi" calls a VIM that is in that package. If I delete that VI the build works fine. Is this a known limitation that a package can't be built, if a VI calls a VIM? Here are the errors seen when the build fails. Thanks. Variant Repository Source 2017.zip
  14. So if anyone is interested in the second half of my post, I've attached a VI that does what I was suggesting. It takes a list of Installed Files which the Post-Install VI can return. Then for all Libraries and Classes it looks at the members, and find where they are on the palette and finds the most root MNU file installed and sets the default menu to this palette. So for instance if you have a palette with an Advanced subpalette, all members in that Advanced palette will actually point to the root palette when you right click which is think is a normal work flow since the right click doesn't give bread crumbs to navigate up, only down. I intend on using this in my package building instead of the built in function because of its support for multiple classes and libraries within a package. Set All Libraries and Classes Default Palette.vi
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.