Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


LogMAN last won the day on May 26 2021

LogMAN had the most liked content!

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

LogMAN's Achievements


Apprentice (3/14)

  • Dedicated Rare
  • One Year In
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare

Recent Badges



  1. Cross-post: https://lavag.org/topic/22821-remove-block-diagram-after-build-with-vipm Please always include links when posting in multiple forums. This appears to be a potential bug in newer versions of VIPM. Here is a related topic:
  2. I'm running VIPM BETA (build 2746), which shows an unusual average CPU load of 3-5% when the package manager is open and 10-15% when a package build specification is open. These values are a bit too high for my taste. A comparison with VIPM 2019 shows an average CPU load of 3-5% in both cases.
  3. I have upgraded to the latest build 2746 and can confirm that it is working now 👍
  4. Great job! Built 2746 properly disables the save button during the build process.
  5. I did a few more tests and found that the build fails only when there is a accompanying .vipc file (even if that file does not specify any dependencies). Recreating the file does not fix the issue. The only workaround I found is to manually add dependencies. For comparison, here is a project for which the build succeeds (dependencies were added manually). https://bitbucket.org/drjdpowell/jsontext
  6. So there is this new checkbox which isn't explained anywhere. What does it do?
  7. You can clone the repositories from GitHub and try yourself: https://github.com/LogMANOriginal/LabVIEW-Composition https://github.com/LogMANOriginal/JSONtext-Object-Serialization I should probably mention that I'm using LabVIEW 2021 BETA (21.0b10) for the build.
  8. Not sure if I'm doing something wrong, but the build process always fails for me and the error message is not helpful (see below). I have mass-compiled the project and found no broken VIs (build passes with VIPM 2019.0.0). Steps to reproduce Open a package build specification Press Build Package
  9. The final message might be due to the build actually failing. I receive the same error when I don't try to break things.
  10. Steps to reproduce Open package build specification Increment the package version (save button must be active - don't press it yet) Press Build Package Notice that the save button is active during the build process. Press Save Package Project The configuration is saved and the dialog will return to edit-mode (build process is still running). After a few seconds the build process fails with an error.
  11. Thanks! By the way, the link on the download page still says "VIPM 2020", although it correctly links to the 2021 discussion forum.
  • Create New...

Important Information

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