Jump to content

Jim Kring

JKI Team
  • Content Count

    1,666
  • Joined

  • Last visited

  • Days Won

    37

Jim Kring last won the day on March 26

Jim Kring had the most liked content!

Community Reputation

69 Excellent

6 Followers

About Jim Kring

Recent Profile Visitors

26,237 profile views
  1. Hi Chris. I don't think there's a way to do either of these, currently, via the API. They are both great ideas and I support them Would you be willing to post these ideas to the VIPM Idea Exchange?
  2. Here are some links: https://blog.jki.net/jki/introduction-to-jki-json https://github.com/JKISoftware/JKI-JSON-Serialization There's not much documentation, since it's a very simple serializer.
  3. Hi Albert, Thanks for reporting this. Yes, you should certainly contact CPE regarding this issue. It would be great if VIPM could detect this, yet I think that it might be tricky to try to guess the developer's intentions. Maybe VIPM could warn the package developer of potential problems. -Jim
  4. Hi @maristu. We have a fix for this issue in the VIPM 2020 Beta. Thanks again for reporting it. If you'd like to help test, please sign up for the beta.
  5. That's great that this LUT approach with in-line execution mode will work for you. Yes, it should be a lot less maintenance in the future. I'm glad it's looking like a good path forward. Thanks for letting us know how it goes. I've learned a bit from this discussion, too.
  6. Yes, I’m pretty sure that if you use an array constant for your sparse values and you use a constant enum to index into that array, then labVIEW will constant fold the array indexing and look up. if you do this in a subVI, to use that look up in several locations, then you’ll probably need to set this up VI execution mode to in-line into the caller, in order for the constant folding to work I’m the calling VI. That being said, if the enum integer values are used as the indices into your look up array, then the operation should be lightning fast.
  7. @Voklaif We dug into it and it turns out to be a LabVIEW bug. The solution is for the user (you) put a To Variant function before the call to Flatten to JSON String, since the bug seems to be inside the coercion dot (and the To Variant function doesn't seem to have that problem). Note: here's the bug (and fix) reduced to a very simple example (example VI also attached for anyone who wants to play with it)... Coerce to Variant Fail (LV2019).vi
  8. This looks like a bug. (Note: I've filed a bug report in our issue tracker here: https://github.com/JKISoftware/JKI-JSON-Serialization/issues/34) I see the same thing as you. The "bridge_data" is missing, here, when it's the only element in the cluster. However, if I add another element next to the variant (so it's not the only element in the cluster) then I see "bridge_data" in the JSON string. JSON Test ignoring single variant in a cluster.vi.zip
  9. I've seen similar problems when VIPM gets an error checking the network for the package repository feed. If we solve the first issue, the second problem will go away.
  10. A.) Is it a "System" package that you're looking at? B.) Or, did you set the Target to System and then are you looking at a LabVIEW package?
  11. One more idea... Is the clock (date/time) set correctly on that computer? If not, that can cause HTTPS connections to fail, since the certificates can't be verified correctly.
  12. The hover effect does not show when the VI is in Edit Mode. It should work OK when the VI is running or when it's in Run Mode (tip: use <Ctrl+M> to toggle between Edit and Run mode).
×
×
  • Create New...

Important Information

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