Jump to content

Jim Kring

JKI Team
  • Posts

  • Joined

  • Last visited

  • Days Won


Jim Kring last won the day on May 15

Jim Kring had the most liked content!


About Jim Kring

Recent Profile Visitors

29,519 profile views

Jim Kring's Achievements

  1. @Steen Schmidt I agree with you about leaving dependencies in their place by default -- we actually do that. It's simply that "C:\Program Files" (and the '(x86)' variant) wasn't on the list of locations where external components were expected. As always, things get a little tricky trying to support decades old paradigms. Regarding a fix for this issue, can you try 2024.3.2761-rc2 here 👉 https://www.vipm.io/desktop/versions/ This should leave anything found under "C:\Program Files" or "C:\Program Files (x86)" along and not build it into the package.
  2. @Steen Schmidt I agree that this is something that needs a fix. I’m trying to think of there is ever a situation where it is desirable to have the current behavior. I can’t think of any off hand.
  3. VIPM 2024 Q3 Release Candidate 1 is now available for testing: https://www.vipm.io/desktop/installer/vipm-24.3.2759-rc1-windows-setup.exe/ Some Key Improvements Improved performance of package info downloads Improved package building when VI dependencies are moved on disk (and linkages have changed) Improvements for projects and packages that contain and call Malleable VIs (VIMs) Better integration with JKI Dragon
  4. Hi @TimE, there's a download link for 2024.3.2759-rc1 on the https://www.vipm.io/desktop/versions/ page. Thanks for trying it out and letting us know how it works for you. -Jim
  5. Hi @TimE I believe that this is related to this issue: https://github.com/vipm-io/vipm-desktop-issues/issues/44 We have a newer build of VIPM 2024 Q3 that I’d love for you to test to see if it work better for you. I’ll share a link shortly. Jim
  6. This is a Pro feature: saving all your project’s packages into a VIPC file: https://support.vipm.io/hc/en-us/articles/214135883-How-to-use-VI-Package-Configurations-VIPC
  7. > (Apr 14, 2023) > 3. Add a mass compile post-install step to avoid bitness-related load warnings when opening the code for the first time after install. @Darren is this load warning a LabVIEW “bug”?
  8. @Bob Schor you'll find the actual packages in the C:\ProgramData\JKI\VIPM\cache folder. You can copy those to another computer and install the packages.
  9. Thanks for reporting this @jyoung8711. FYI @Rolf Kalbermatter
  10. Hi @hooovahh, I didn't realize that this library offers support for spanning TDMS. I'm going to take a look at this right away... 👍 Thanks for the great tool!
  11. @Zaphiro Technologies CC: @RolfK There is a cross-platform shared library naming trick. (It could be that the package build process messed up the paths when writing linker info.) See: LabVIEW Help >> Configuring the Call Library Function Node
  12. @JKI-OfAllTrades I'm not sure about that. I think that, in general, most of the community has moved to LV2020 as the standard version for open source/community tools. You could reach out to some of the folks in the DQMH forum.
  13. Hi @JKI-OfAllTrades, Looking at the VI Peek package info, I see that it's compatible with LabVIEW 2020 or greater, which is why it's not showing in your package list. Note: In the VIPM Settings window you can show all packages, even if incompatible with the selected LabVIEW version. However, you won't be able to install it. One idea is to download the source code and then use LabVIEW 2020 Community Edition to Save For Previous into LV2017. Good luck!
  • Create New...

Important Information

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