Jump to content

Jim Kring

JKI Team
  • Content Count

    1,364
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by Jim Kring

  1. Hi @Ben Stern. That's an interesting question, and I can see how it would be very useful to have the VIPM API working on Mac. It's not currently possible (meaning, the VIPM API won't work on Mac). I don't have much experience calling built LabVIEW apps on the Mac from the command line with arguments. Do you know if it's even possible? On Mac, Applications that run in Finder are a little bit different than command-line executables (but, keep in mind that I'm not a Mac expert). I'm thinking there's probably a way to make this all work, since it's only software...
  2. I’ve created an issue in github for tracking the fix for this: https://github.com/JKISoftware/JKI-VI-Tester/issues/12
  3. Hi Norm (@Viper). Great question and you're not the first one to want this feature -- I'd like it, too. No, right now that's the only way to do it -- by unbundling and building a cluster of data yourself. EasyXML doesn't look at the data inside of classes, unfortunately.
  4. That's great that you can see the packages, now. Can you describe what you mean by a "MacOS JKI VI Tester" package? I'm assuming this might be the special Mac-compatible package I shared with you yesterday. We didn't actually make that available to the public inside VIPM -- my guess is that it says "unreleased" in the repository information.
  5. Hey @trobertson79, we found and fixed an issue on the VIPM package server that was affecting Mac users (that I was able to reproduce on Mac). I just tested the fix and it's working now for me (tested on my Mac). Please let me know if it's working for you.
  6. That's great! If you mass compile (Save All) the code, does it continue to ask about registry.dll? You may need to Ctrl+. to stop the VI Tester UI and then do a Save All. Or, you can mass compile the installation directory. Thanks for letting me know.
  7. OK, I just checked and the VI Tester package claims that it only works on Windows. I'm not sure why that's the case, or if it's true -- my thought is that this should work just fine on Mac and Linux. I've repackaged VI Tester such that it should install on Mac. Can you try this package (link below)? jki_labs_tool_vi_tester-2.0.0.285-2.ogp Please let me know how this works for you.
  8. Hmmm, I'll look into it -- I've VIPM for Mac on my computer. It might be a network issue. Stay tuned...
  9. Hi Thomas. I'll do my best to get you going. First off, which version of LabVIEW are you using? The issue could be related to the fact that the latest version of VIPM for Mac is an older version of VIPM. And, yes, the vipm:// weblinks don't work on MacOS, unfortunately.
  10. Hey Grant & Joseph, The issue is that in a built application, if there's no Window (Front Panel) open, then Windows will force the application to stop -- it just pulls the plug on it. I guess that makes sense, since it is "Windows" after all. For JKI State Machine's running as the Top Level UI of a built EXE, you'll want to make sure that they don't close the front panel until after all execution is complete. One way you can "close" the front panel without it being killed by Windows, is to set the FP State to "hidden".
  11. Hey Brian. I just asked about this, and the primary thinking is this: even though it's a no-op, it serves to document how to user the "Data: Cleanup" frame. Also, in the case where someone might change the VI Reference constant to an Open VI Reference, it's helpful that we're actually closing it. Why would someone call Open VI Reference? I'm not sure, but one thing I thought of is when a VI wants to hold a reference to itself open, so that if it's Front Panel isn't visible and it's running because someone else opened it by reference to it, then it won't be "garbage collected" (aborted and destroyed) when the reference count goes to zero (since it won't go to zero if it opens an explicit reference to itself). Does that make sense? Do you have any thoughts about that?
  12. Hi Jim, Thanks for your patience in waiting for a response. That's great that you're helping your colleague's learn LabVIEW and how to use the JKI State Machine. We're actually working on some presentation/training material for new users. For now, I would recommend: Watch Video Tutorials Learn Best Practices Use the JKI State Machine Editor
  13. The JKI State Machine for LabVIEW is an easy-to-use yet powerful state machine template. It is the very same template that is used by the JKI team, nearly every day, and is the result of years of refinement by our team of LabVIEW™ experts. JKI State Machine Project Homepage Get JKI State Machine Watch Video Tutorials Learn Best Practices JKI State Machine Editor
  14. Hi Fabiola. That's fair. I guess I'm trying to figure out the volume of support calls. The solution for users is to upgrade VIPM (assuming they can), so the presumed support impact is low. Of course, that's unknown to you (or do you have information/data about it actually being a support problem)? Hi Chris. We haven't officially abandoned Mac and Linux. We may decide to release a new version for Linux and Mac, if there is enough customer need.
  15. Hey Fab, Users of older versions of LabVIEW are able to easily upgrade to newer versions of VIPM -- right now, the error dialog users see when they try to open a package that's an older format could be more helpful in suggesting an upgrade (via check for updates, right in that workflow). Is upgrading to newer versions of VIPM a problem for your users? Do you have data on how many of your users can't upgrade to the latest version of VIPM (for one reason or another)? Do you know what's preventing your users from upgrading? I'm sure you can appreciate that investing development resources in features that disincentive upgrading, in most cases, probably doesn't make good business sense. It probably makes more sense to invest those resources into features that make it attractive for users to upgrade. Of course, it's all a balance. -Jim
  16. Sorry for the delay in response, James. I think this could (in part) be because VI Tester has not been mass compiled. If you mass compile it, does it launch faster? Or, do you think it's a function of the number of tests in your project? -Jim
  17. JKI REST Client is a HTTP client library for connecting LabVIEW applications with RESTful web services. JKI REST Client provides a client implementation of HTTP protocol that is specifically designed for integrating LabVIEW applications with web services. JKI REST Client augments the LabVIEW native implementation of HTTP by adding several features that make it better fit for connecting with RESTful web services than LabVIEW native HTTP client. HTTP REST Client Homepage Get HTTP REST Client
  18. I just fixed the Knowledge Base link, thanks. Yes, that's the work-around we're proposing. For what it's worth, the bug traced back to a cluster constant on the block diagram that had the wrong cluster order for Client ID and Server ID. It was very hard to track down, since it looked like everything was working -- the swapping of values actually happened right at a dynamic Call by Reference of a VI that has its FP controls hidden (so can't debug) and BD password protected
  19. Hi Steen, David. Big apologies for the long delay in resolving this issue -- I wish I had a good excuse for that, but I don't, other than it was tricky to track down the root cause and it wasn't prioritized. Fortunately, there is a simple work-around for VIPM 2014 - VIPM 2018 (see Knowledge Base: Deactivation Fails for Licensed Add-ons built with VIPM) and a fix coming in VIPM 2018f1.
  20. VI Package Manager (VIPM), JKI's flagship toolkit ships with LabVIEW and allows you to discover, create, and share LabVIEW add-ons. VIPM gives you instant access to the add-ons on the LabVIEW Tools Network. Get VIPM, Learn More Release Notes, Knowledge Base, Idea Exchange
  21. This issue has been resolved in VIPM 2018. Stay tuned and let us know if you need early access.
  22. Caraya is an assertion and unit test framework for LabVIEW that is simple and fast. It takes a whole new approach to unit testing; your VI is your test. Caraya allows you to convert your manual test VIs you use to debug your code into unit test cases with nearly no effort. This significantly lowers the barrier to systematicaly write unit tests for your project leading into improved overall code quality for real-world projects where developers don't always have the luxury to write unit test cases first. Caraya Project Homepage Get Caraya
  23. Update: I've added a little bit of documentation about this, here: https://github.com/JKISoftware/JKI-EasyXML/blob/master/README.md#reading-raw-xml-into-strings-using-the-xml-suffix-in-string-labelname
  24. Update: I've added a little bit of documentation about this, here: https://github.com/JKISoftware/JKI-EasyXML/blob/master/README.md#reading-raw-xml-into-strings-using-the-xml-suffix-in-string-labelname
  25. Hi James, Thanks for posting your observations and concerns. We have made no plans to stop development or fixing bugs -- yes, things have slowed down a bit. For what it's worth, I fixed a couple bugs and made a minor performance improvement last week, that will make it into the next release. Thanks for your patience and feedback. Is there anything critical on your organization's list of needs? -Jim
×
×
  • Create New...

Important Information

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