Jump to content

Jim Kring

JKI Team
  • Posts

    2,021
  • Joined

  • Last visited

  • Days Won

    77

Everything posted by Jim Kring

  1. Great question! They have to have a VIPM.io user account and have their gitlab/github usernames added in their VIPM.io profile.
  2. Thanks. We've seen this before. It's an issue with the curly quotes not working in the updates information file.
  3. Hi Zachary, Can you try opening the VIPM Main window and refreshing the package list? 1) Click on the orange "VI" in the upper left corder of the window in your screenshot 2) Click the refresh button 3) Search for DCAF CVT
  4. The package's homepage on vipm.io has a direct download button. Does that work for you? https://www.vipm.io/package/ni_lib_dcaf_cvt/
  5. Thanks for that info. Just to be clear: Is this a separate issue or does changing to "UTF-8 without signature" fix the original issue?
  6. Thanks for the update. I haven't looked into it deeply, but I found a couple links that seem informative: https://stackoverflow.com/questions/10715001/bstr-to-cstring-conversion-for-arabic-text http://www.delphigroups.info/2/f5/481372.html If you're able to figure this out, it would be a great improvement to the library.
  7. Thanks for clarifying all the different things you’ve tried. I’m sorry that the instructions aren’t working correctly for Arabic. I don’t have any experience getting this tool working for Arabic, so I haven’t run up against this problem. I’ll ask some of my colleagues if they know anything about it
  8. I haven't tried, but I would assume that it already is compatible with Arabic. There's a documentation guide here to help you out: https://github.com/JKISoftware/JKI-Simple-Localization/wiki Please let us know how this works for you.
  9. Great idea, Joerg. This is not currently a feature, but it's worth considering, for sure. Your use case sounds valid.
  10. Thanks for the clarification on your use case -- it's very helpful (and exciting) to see the code in action that does the automated builds of your VI Packages! We've done some work on a fix for this issue (we're calling it a "bug") and I'll ping you off-line so you can test it out, if you'd like.
  11. Hi Joerg, Great idea. A couple comments/questions: I see that the VI Package Builder GUI defaults to 1 for the major version, yet it allows changing it to 0. It also allows you to build and install such a package (with 0 as the major version), just fine. More so, I see there are several packages in the wild (on vipm.io) that use 0 as the major version number, too. So, it would seem reasonable to allow the VIPM API to support this, too, and it wouldn't introduce any new problems. Which VIPM API VIs are you calling and how you're using it? I'm assuming you probably have an existing .vipb file and you're using "Read VI Package Build Spec.vi" and then "Write VI Package Build Spec.vi" to update a value such as the build number, as shown below. Thanks for posting the idea and for your additional input.
  12. Hi Alex, This may not be trivial, although it's probably technically possible. I'll ping you off-line. -Jim
  13. Ah, OK. Thanks @Sam Grayson. It's helpful to know that the issue may have something to do with .NET.
  14. Hi @Mathilde (CC: @Francois Normandin) Thanks for your interest in code coverage with Caraya. There's not currently a built-in feature for doing code coverage in CaraYA. Do you have thoughts on how you would want to calculate coverage? I've implemented some simple coverage tools in projects by using naming conventions for my tests and enforcing that each public member of a library has a test associated with it.
  15. That's strange. I wonder if there's some kind of permission issue. Does "Everyone" have Full Control on the "C:\ProgramData\JKI\VIPM" folder?
  16. Hi Peter, Can you try exiting VIPM, deleting the cache folder, and then restarting? C:\ProgramData\JKI\VIPM\cache
  17. Hmmm... which "list" are you referring to? The main VIPM package list or the Dragon project's Resources tree/list of packages? Also, can you look in the "C:\ProgramData\JKI\VIPM\error" folder to see if there's any error messages logged?
  18. Hi @Yann. Thank you for sharing how IT resolved the issue for you. That's really helpful to know.
  19. Hi @Sam Grayson and @Yann -- I'm also curious to learn more about how to configure Cybereason so that VIPM will work OK for you. Please let me know if your IT departments are willing to share more information.
  20. Hi @Mario. Great question. As @James@Work point to, VI Package Configurations are a great solution for keeping track of the packages in your project. Additionally, JKI has announced the beta for Dragon, which sits above LabVIEW and VIPM to provide high-level management of LabVIEW projects and configurations of packages used by your project.
  21. Fantastic! Glad to hear you're up and running.
  22. I've seen that before -- sometimes VIPM's local package database doesn't get fully sync'ed Please try this: Open the VIPM Main window by clicking on the orange "VI" Then, refresh the package list in VIPM by clicking the refresh button on the toolbar You should then be able to find OpenG Toolkit by clicking on the link again or searching for it in the VIPM Main window.
  23. That’s a great idea to show the build output, Joerg. I assume by “feed back the progress” you mean that you would like to see some progress text output to the standard output, which the CI is showing in the console?
  24. Totally. I've opened a service request with NI to dig into it some more. I'll post updates, once I find out more.
  25. I was able to reproduce the issue with the help of a colleague who has an RT Target. I've written up some info about this issue here: https://lavag.org/topic/21753-1d-array-to-string-not-compiling-correctly/ OpenG String v4.1.1.16 should fix this issue (although it's simply working around the LabVIEW compilation bug, which could potentially be causing other issues) I'm going to work to report this to NI, since we can reproduce the issue.
×
×
  • Create New...

Important Information

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