Jump to content

Jim Kring

JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Jim Kring

  1. Hi All, @QsiAtWork, @Nstewart, @szymsciupak, @Mads Toppe, @wolfkil VIPM 2020.1 for Windows and Mac are available for download at vipm.io/download This new version allows download without sign-in, to allow corporate users behind an IT proxy/firewall to download/install packages. Thanks for your patience. -Jim
  2. Another thought... you can append text to VI Descriptions via this setting in the package builder.
  3. Hi Olivier, My first thought is that this would probably only work for a post build custom action (unpack the VIP, modify the VIs, and repack the VIP). -Jim
  4. Hi @Paul Torek. We did have some issues with VIPM 2020. There should be fixed/improved in 2020.1. You can get the latest release candidate and help us test in the VIPM 2020 beta forum. Sign up here to get access to that forum.
  5. Hi @drjdpowell, @jb1592, Sorry for the issues. We're working hard on VIPM 2020.1 and hopefully this issue will be resolved. It's odd that the package builder window opens, yet the VIPM main window and the system tray icon aren't showing. I've heard a few other reports of similar behavior and we've got it on our radar. I don't think it's related to the "Error 42 occurred at (http response "404". URL Requested)" -- I think that was an issue with a missing file on NI's LVTN package repository. Regards, -Jim
  6. Hi @Vollinger. The issue is that LabVIEW addresses items in the palette by their display name. So, if two items have the name "Connect.vi" then LabVIEW will show the first one it finds, even if it's for a different toolkit. The solution/work-around is to change the palette display name of your "Connect.vi" to something like "Connect (MyComponent)". Here's where you would change that name in the palettes, via the palette editor. Does that work for you?
  7. HI @JMA_1. We made some major installer improvements in VIPM 2020.1. We have a release candidate available for download in our beta testers forum -- sign-up here to access that forum. Thanks and hope we can get you working quickly!
  8. Hi @kosist and @wolfkil. We're working hard on a VIPM 2020.1 build. There are lots of improvements, one of which is that it does not use a sign-in to download packages from the VIPM Community Repository. You can get the latest release candidate and help us test in the VIPM 2020 beta forum. Sign up here to get access to that forum. We're working hard to make VIPM work well with new versions of LabVIEW. This latest 2020 release was difficult to full test, due to COVID-19 during the beta and launch, and a reduced number of beta testers. We're hoping VIPM 2020.1 addresses the issues peop
  9. Thanks for letting us know, James! Yes, 2020 had a lot of work put into it and the beta/launch was in the middle of COVID-19, so things didn't get as many eyes as usual. We do have a version 2020.1 in beta right now (if you can't access this, please be sure you sign up for the beta and/or send me a PM).
  10. Hi Dan, Glad you're exploring VIPM 2020. What do you mean by "load packages"? Are you saying that you'd like to add them to VIPM's package list? You can double-click the package and open it in VIPM to install it. Also, in VIPM 2020.1 (currently in beta) we've added an "Add to Library" right-click option on Packages in Windows File Explorer. Does that answer your question? -Jim
  11. Glad you figured it out, @Justin Thomas, and it was just an email issue. Hope Design Palette is working well for you.
  12. Hi Everyone @Mads Toppe, @szymsciupak, @wolfkil, This is a known issue that affects some people behind corporate firewalls. In VIPM 2020.1 (still in beta), you will be able to download packages without a sign-in and hopefully this will resolve the pain point. Thanks for your patience. -Jim
  13. Hi Antoine, Thanks for posting this. I'm not sure what the issue is. I don't see the same thing. One thing that's different between your and my systems is you have a version "1" in the list. Would you be willing to send me a copy of that package? I suspect it's not a released package, but it appears to be causing some issues. Don't delete it quite yet, because I'd love to know what's going on.
  14. Hi Thomas, Actually, we use some 32-bit shared libraries, including OS libraries and also some 3rd party libraries, like the OpenG Zip Tools. For the MacOS beta, VIPM migrated to using command line zip/unzip tools and dropped a couple minor usability features that maybe nobody will notice (like extracting lvlib/lvclass icons from the XML file, which requires zlib deflation). However, for MacOS, we figured it was better to have things mostly working OK in 64-bit than not at all. For Windows, we wouldn't want to lose any functionality. I hear you about the memory limit issue. I hope
  15. Hi @ThomasGutzler. Thanks for the great idea! I'm curious what you need 64-bit support for, specifically? Are there any problems created by having VIPM for Windows be a 32-bit application? Would making it 64-bit help in specific ways? Thanks for letting us know.
  16. This is in currently in progress. If you're in the VIPM 2020 Beta you can help us test it, when it's ready.
  17. Hi Sam. I'm going to check on this right away. Thanks for reporting this. Hopefully, we can get you going...
  18. Oh, it looks like you actually have the Flat UI Controls (and the OpenG Toolkit) package installed, but the JKI Design Palette is not installed -- that's expected. If that's correct, the Flat JKI Controls will be located on disk here: Do you see those?
  19. Hi Scott, The JKI design palette is currently only Windows compatible. I could look into what it would take to get a Mac build working. It’s distributed as a PPL, and has to be compiled in each platform. you can choose to ignore the dependency, and continue the installation of the flat UI controls. You would then need to browse to the installation location do use the controls. thanks for your patience. As you know, we just got VIPM 2020 working on MacOS Jim
  20. The VI Package Builder could specify the name of the VI to show in the palettes, or be smarter in general about which VI to show in the palettes. Sometimes it opens the wrong VI.
  21. Some advanced users are asking for support to install VIPM for Windows onto a Docker container. This would allow creating fully automated build processes that spin up virtual machines that have LabVIEW and VIPM installed on them, so that VI Packages can be created automatically.
  22. Hi Thomas. That’s super cool! Thanks for showing the screenshots. I’m glad to hear how easy that was for you and hope it’s helpful to you and your team. -Jim
  23. I’m glad to hear it’s working for you!
  • Create New...

Important Information

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