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.