Jump to content
The search index is currently processing. Activity stream results may not be complete.

All Activity

This stream auto-updates

  1. Last week
  2. Hi, It's still interfering with QuickDrop (ex: QD -> ctrl+I then the Palette appears). Today it appears with ctrl + Alt (without QD). When it's installed it works well, but after a while it interferes. I have to uninstall the palette each time I don't need it. Regards,
  3. Earlier
  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. Updated. This is a great tool by the way. Thanks for publishing it.
  6. 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
  7. Is there a way to have the tool recognize multiple axes on a single chart? When I pull the json file using the JKI Localization Tool there is only a single Y-axis called out.
  8. Hi @Sahithi I think that, because of the way LabVIEW works, you will need to rebuild the package altogether.
  9. I have a LabVIEW add-on that is licensed using Protection Plus 4 and packaged using VIPM. There are some bugs that require replacement of some Sub VIs of the licensed library. When trying to build a package (intended to be a patch) with the fixed sub VIs, the VIPM throws library dependency errors. What is the available solution for bug fixing in this case? Apart from building next version of package altogether?
  10. I have a LabVIEW add-on that is licensed using Protection Plus 4 and packaged using VIPM. There are some bugs that require replacement of some Sub VIs of the licensed library. When trying to build a package (intended to be a patch) with the fixed sub VIs, the VIPM throws library dependency errors. What is the available solution for bug fixing in this case? Apart from building next version of package altogether?
  11. I'm running VIPM BETA (build 2746), which shows an unusual average CPU load of 3-5% when the package manager is open and 10-15% when a package build specification is open. These values are a bit too high for my taste. A comparison with VIPM 2019 shows an average CPU load of 3-5% in both cases.
  12. I have upgraded to the latest build 2746 and can confirm that it is working now 👍
  13. Great job! Built 2746 properly disables the save button during the build process.
  14. 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.
  15. 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
  16. While creating some more screenshots for this post, I actually figured out the problem: It's in the URL of the repo! On the VM where I got the error message, I had not provided the scheme (the protocol, https). It is a bit misleading that the error message (as shown above) will actually display the full URL including the scheme.
  17. Hey VIPM team, we're experimenting with local VIPM repositories but running into problems. We're working in a VM running LV2016 and VIPM 2021.0 (2721) We set up a local repository which should be accessible via the URL https://vipm.hampel-soft.com/ (private, only available internally or via VPN) When trying to update packages, VIPM throws an error In the error logs, there actually is an error associated with the file VIPM wants to download from our custom repository: =========== START of VIPM 2021.0 (build 2721) Error Message =========== An internal VIPM 2021.0 (build 2721) Error has occured on: Sunday May 30, 2021 at 10:02:18 AM = Automated Message Start = Error 42 occurred at (http response "HTTP/1.1 400 Bad Request". URL Requested: https://vipm.hampel-soft.com/index.vipr.zip) 52D9A4562D38CB99A669F85011D9D2EE:1310001 in 9B2F9930B5E536BF44B4C52F860D615E->1C6929D1E714EC131EBDBC872009DE5E->6A6376334CDCAB91B9771788751EE7B6 ->OGPM Class.lvlib:E4D4F8782AE9DBB9105BB3D92B765ACC->OGPM Class.lvlib:8C3E06FF1E6C98D9A8E16799D6B3EEEB->7AF8C3BAECF0AACE1A61F9248BAC879A->VIPM Main Window.vi Possible reason(s): LabVIEW: (Hex 0x2A) Generic error. = Automated Message End = = User Defined Message Start = Error downloading from: - https://vipm.hampel-soft.com/index.vipr = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 7AF8C3BAECF0AACE1A61F9248BAC879A-> OGPM Class.lvlib:8C3E06FF1E6C98D9A8E16799D6B3EEEB-> OGPM Class.lvlib:E4D4F8782AE9DBB9105BB3D92B765ACC = Error Handler Call Chain End = =========== END of VIPM 2021.0 (build 2721) Error Message =========== Wireshark shows that the HTTP request is denied with a strange error message (see screenshot): Both through the browser and via a simple test VI, I can manually access said file on that LV2016 VM. I then tried adding our repo within another virtual machine running LabVIEW 2018 and VIPM 2021.0 (2694); here our repo works fine! After upgrading the installation in the LV2018 VM from build 2694 to build 2721, our local repo still works for that VM. So it's not related to the VIPM version it seems.
  18. I also faced same issue, I was able to resolve this by using following command in the terminal. ensure you provide root folder where labview is installed in your system sudo chmod -R u=rwx,g=rwx,o=rwx <labview application path>
  19. 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
  20. 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
  21. OK, we've found and hopefully resolved the issue. The fix will be in the next nightly beta build.
  22. OK, we've found and hopefully resolved the issue. The fix will be in the next nightly beta build.
  23. 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.
  24. I've checked, my package does not depend on any other package. There was an vipc file (1kb), I deleted it, forced VIPM 2021 (2745) to check again for dependencies (still none) no *.vipc file created next to my *.vipb file package creation still fails.
  25. sorry, right after posting this I went to check if this issue had already been reported... it seems it has :
  1. Load more activity
×
×
  • Create New...

Important Information

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