Jump to content

Jim Kring

JKI Team
  • Posts

    2,023
  • Joined

  • Last visited

  • Days Won

    78

Jim Kring last won the day on August 18

Jim Kring had the most liked content!

5 Followers

About Jim Kring

Recent Profile Visitors

28,151 profile views

Jim Kring's Achievements

  1. Hi Jaun, To fix this, can you try running this exe as Administrator (it should ask you to run as Administrator when you double click it): "C:\Program Files (x86)\JKI\VI Package Manager\support\VIPM Update Registry.exe" Please let me know if that helps. -Jim
  2. Hi Sam. I'm sorry for the trouble. This is really a pain... Can you try using this copy of the "VI Package Manager Runtime Engine" installer? >> vipm-2020.3.2540-windows-prerequisites.zip << This is a copy of the actual temp folder (containing the VIPM runtime engine) extracted during the VIPM 2020.3.2540 installation. C:\Users\%USERNAME%\AppData\Roaming\JKI\VI Package Manager 2020.3\prerequisites If that doesn't work, we could try the one from the 2020.3.2532 installer.
  3. Hi,

    I was curious if it's somehow possible to send an array to JSON?

  4. 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.
  5. 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
  6. Hi @Sahithi I think that, because of the way LabVIEW works, you will need to rebuild the package altogether.
  7. 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.
  8. 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
  9. 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
  10. 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
  11. OK, we've found and hopefully resolved the issue. The fix will be in the next nightly beta build.
  12. OK, we've found and hopefully resolved the issue. The fix will be in the next nightly beta build.
  13. 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.
  14. 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!
  15. 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?
×
×
  • Create New...

Important Information

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