Jump to content

Jim Kring

JKI Team
  • Content Count

    1,718
  • Joined

  • Last visited

  • Days Won

    42

Everything posted by Jim Kring

  1. Thank you for posting this! I'll forward it along to NI to take a look into it. Well, only NI can fix LVInternal errors 🤷‍♂️ Still, I'll ping them, since I'm sure they care to know what the issue is.
  2. You're welcome. Any requests to make it more awesome?
  3. Hi Sam. VIPM 2020 works a little bit differently. It hangs around in memory for a little bit in case someone uses it again -- this way, it's much more responsive. Yet, it's changed the observed behavior around exactly when the package list refreshes. This is something we're working on and should be improved in the next release.
  4. I think the issue is that you need to "Check Network for Package Updates" (Refresh) in the main VIPM package list. Can you try that? Then, I think it'll find the new version. LMK if that works. PS - you're welcome!
  5. Hi There! Glad you like the JKI HTTP REST client. For the base URI, I would use: http://192.168.0.100/restapi and then for the path when you call GET or POST, use: /relay/outlets/0/state/ Here's how you could add the X-CSRF header. Note that you can type (or copy-paste) new items into the drop-down selector for the header -- it works like a string control, but with some pre-defined options to make life easier for common headers. The JKI HTTP REST Client passes the username and password into the HTTP VI used by built-in HTTP Open Handle.vi, which I believe doesn't support digest authentication. Under the hood... Digest authentication is something that could be added -- here's the specification and here's a demo server, if you're interested in trying.
  6. We just released a new build with 2020 support https://www.vipm.io/package/jki_design_palette/
  7. There’s a new build of the JKI design palette that supports LabVIEW 2020! https://www.vipm.io/package/jki_design_palette/
  8. Hey @John Hoehner and @ChrisStrykesAgain. Caraya 1.0 is officially released and in the wild! https://www.vipm.io/package/jki_lib_caraya/
  9. Yes! Thanks for the ping about this Sam. We will update this, very soon.
  10. VIPM 2020 is sporting a completely new visual design that's both more modern and fun to use! We based it on the JKI Flat UI Controls 2.0. Here are a few screenshots below! You can download VIPM 2020 today! Main UI Package Builder Options Window VIPM Browser (more details here) Windows System Tray Notification (more details here) Download VIPM 2020 today!
  11. We're not yet ready to release VIPM 2020 for Mac. If you want to be notified when it's released, please subscribe to this forum topic.
  12. Hi @trobertson79. It's a great question! The sort of simple answer is this: In most programming situations, the developer should pick one way or the other (either add to front or add to back). Mixing front and back is a recipe for hard debugging. And, since the template already enqueues at the front then this is why we recommend to stick with that.
  13. 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?
  14. 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.
  15. 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
  16. 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.
  17. One nice feature of VIPM 2020 is that it detects which LabVIEW version is active and will automatically "target" that LabVIEW version (and it's smart about when you change the target). After using this a while, I've found that I can safely forget about having to tell VIPM Browser which LabVIEW version I'm using (since I have years of experience setting the target drop down in the VIPM Main listbox). In VIPM Browser, there are cases where you have more than on LabVIEW version open and you might need to be certain about which LabVIEW version is actively being targeted. When more than one LabVIEW version is open, VIPM Browser displays which version is active/targeted by VIPM, and displays that LabVIEW version in the titlebar. Download VIPM 2020 today!
  18. 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.
  19. 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.
  20. @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
  21. 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
×
×
  • Create New...

Important Information

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