Jim Kring

That's great! If you're up for a little challenge, you could made the change to the source code on GitHub as a Pull Request. https://github.com/JKISoftware/JKI-Simple-Localization This would help ensure that future releases are compatible with your local modifications.

That's a great idea -- I don't think it's currently a supported feature. It's definitely possible and I would probably do this (in the code) by adding a key for the additional axis labels: yAxisLabel (maybe also allow yAxisLabel.0 and/or some kind of backward compatibility) yAxisLabel.1 yAxisLabel.2 The code is open source and you could take a look at how to do this. -Jim

Hi @Sahithi I think that, because of the way LabVIEW works, you will need to rebuild the package altogether.

One more thing... Be sure to set up Basic Auth (username/password) protection (or limit access via VPN as you mentioned) if you’re going to let other people know your repository URL.

Hi Joerg, Glad you figured this out. Yes, the protocol (https://) prefix needs to be included. Also, I’m not sure if it’s related, but there’s one extra thing that might be relevant: For HTTPS support in VIPM 2020.x be sure to set the network options in VIPM to “Use System Proxy Settings (Windows Only)”. The “No Proxy (Direct Connection)” setting doesn’t support HTTPS, yet... In VIPM 2021 (now in beta) we’ve added HTTPS support in the default (No Proxy / Direct Connection) mode. -Jim

This should be fixed in build 2746 -- I just tried to build the LabVIEW-Composition library and it seems to work. You can get this latest build via check for updates in VIPM or here: resources.jki.net/en/vipm-2021-beta-download

Hi there. This should be fixed in build 2746 -- I just tried to build the LabVIEW-Composition library and it seems to work. You can get this latest build via check for updates in VIPM or here: resources.jki.net/en/vipm-2021-beta-download

OK, we've found and hopefully resolved the issue. The fix will be in the next nightly beta build.

OK, we've found and hopefully resolved the issue. The fix will be in the next nightly beta build.

Thanks for posting these details. We're able to reproduce the issue our end -- we'll will dig into it and report back here once we learn more.

Hi Antoine, i’m so glad to hear you found the fix to this problem. I suspect the problem happened as a result of a botched update of LabVIEW by NIPM. thank you for posting all of your details here. We will create a VIPM knowledge base entry and link to the NI knowledge base entry, in case anyone else runs into this. thanks!

Hi Antoine, I don't see an f4 patch available for download (e.g. on the LabVIEW Download Page). Can you point me to this update?

Sorry for the delay -- I wasn't getting email notifications of new posts to this forum 🤦‍♂️ I'll look into this right away. Thanks for your patience.

This setting marks that the package can only be installed into the global LabVIEW environment and not a virtual environment. If you want to know more, please sign up for the Dragon beta.

Sorry for the delay -- I wasn't getting email notifications of new posts to this forum 🤦‍♂️ I'll look into this right away. Thanks for your patience.

Oh, no! I'll see if I can get to the bottom of this. Sorry for the delay -- I wasn't getting email notifications of new posts to this forum 🤦‍♂️

Hi There. Unfortunately, there's no `force` option when installing packages that would allow overriding the LabVIEW version compatibility. Which package are you trying to install?

Hi Ivan, This should be fixed in VIPM 2021 beta. -Jim

Thanks! @LogMAN! We've fixed that typo

We're excited to announce the VIPM 2021 beta! You can Download VIPM 2021 Beta Software Here. Note: If you are a JKI Dragon Beta Tester, installing VIPM 2021 beta will remove JKI Dragon. Please do not install VIPM 2021 beta on the same machine on which you wish to continue testing JKI Dragon. What's New: Supports LabVIEW 2021 beta Main UI layout and usability improvements [build 2732] Fix - Installing packages with deep recursion (e.g. A>B>C>A) was getting stuck and hanging VIPM (e.g. SQLite toolkit). This has been fixed. [build 2732] Fix - Detection of project LabVIEW version was not working well if there were no VIs in project. This has been fixed and the LabVIEW version will be read from the .lvproj file. [build 2732] Fix - Missing Friend Classes No Longer Cause Package Build Errors - The package builder was raising a dependency missing error if a friend class could not be found. However, friends are not actually required. Now they don't cause a missing dependencies error. [build 2732] Fix - Improved "Please Wait" Dialog - Fixed text cut off in the Please Wait Dialog [build 2732] Fix - Community Edition was not setting the "Restart LabVIEW After Install" flag in built packages (and other Pro features that are available to Community Edition such as pre- and post-build custom actions) And more...

Hi Jason, I'm glad you got it working. I'm curious if the problem re-appears if you upgrade back to 2020.3, but I'll let you decide when you have the time do that experiment. Thanks again for posting about this issue -- it's helpful to us and other users. Regards,

Hi @Jason Herington. Thanks for reporting this. I haven't seen this specific error before. Does it happen every time? -Jim

Can you try typing this into a terminal? cd ~/Library/PreferencePanes/ This will navigate you into the PreferencePanes folder then type the following: ls This should list the contents of the folder. Do you see something like the following? VI Package Manager.prefPane If so, then typing the following may fix the issue (as described here) by removing the "quarantine" flag in the OS security settings: sudo xattr -d -r -s com.apple.quarantine "~/Library/PreferencePanes/VI Package Manager.prefPane"

Hi Glen, Sorry for the frustration. Mac support has been challenging for VIPM, but we try. It looks from your post that you tried all the tips mentioned on the knowledge base entry here: File Permission Errors running VIPM on macOS The "AppTranslocation" thing in the file path ("/private/var/folders/w7/rtz9k1m114390vq0fxc21bv00000gn/T/AppTranslocation/54274253-33FC-46D0-A566-B7 F86CC7D1F7/d/VI Package Manager.app/support/callbacks.llb/Refresh Menus 2013.vi") makes me curious if this is some new kind of file system thing that we're not handling. I did some googling of "AppTranslocation" and found a couple interesting reads here and here. I'm not sure right this second how to fix this, but we'll look into if. If you're able to figure out a solution, please post back here.

Oh no! I’m sorry to hear the installers and security challenges are such a pain. I wonder if there’s a way to have a VIPM installer that does not include the runtime engine stuff — can you install VIPM and the skip over the runtime installer part, I wonder.