Jump to content

Jim Kring

JKI Team
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Jim Kring

  1. Hi Brian, Thanks for the additional clarification and screenshots. You're 100% right about this -- we've got a bug on our hands. I've filed a bug and added it to the known issues: Known Issue (Case 6125): Installing package with missing dependencies doesn't show warning Thanks, -Jim
  2. Hi Steve, Sorry for the delay in response -- I just got back from the Boston NI Technical Symposium No, EasyXML doesn't handle parsing XML without an input data type. Can you post an example of your XML and how the schema change would break EasyXML? I'd love to brainstorm on how EasyXML could handle this situation. Thanks, -Jim
  3. Brian, Can you please tell us whether you see any warning in the Action Confirmation Dialog? I believe (with about 50% certainly) that VIPM does give you an indication that there are missing dependencies in this dialog. The should be grayed out with a status of "not found" (or similar). If it doesn't give this sort of indicator, then, yes, this is a major bug. However, VIPM should still allow you to install a package that has missing dependencies. The use case for this is when you need a VI in a package that doesn't actually have a dependency on the missing package (since it only takes one VI in a package that depends on another package to create a dependency). Thanks, -Jim
  4. Hi Brian, This is a great suggestion! Currently, there are extensive dependency management features in the VI Package Configuration Editor window, when using VI Package Configurations. Currently, however, the main VIPM window does not show missing dependencies. It's definitely on our road map to add dependency management to the main VIPM window. In the interim, please try to use VI Package Configurations for all your LabVIEW projects. Here's the process we recommend: 1) Apply your VI Package Configuration before starting work on a project --> this ensures that you have all the latest packages installed and that there are no missing dependencies. 2) Scan your project for VI Packages, occasionally, when working on a project --> this ensures that you have all the packages being used on your project in your VI Package Configuration. Thanks, -Jim
  5. Hi Matthew, First, I'm sorry that it took so long to respond. I was traveling to the Boston NITS event when you posted. I'm happy to hear that you got it working. There are a couple possible "root causes": 1) It might have been a permissions issue with files/folders in the Temp directory 2) It might have been that there were files in the Temp directory that were "in the way" and even though VIPM had permission to delete them, it wasn't trying to delete them before writing. If the problem was #2, then this might affect all users -- not just Vista. I'll take a look under the hood and see if I can find anything that looks suspect. Thanks, -Jim
  6. You're welcome. I'm glad to hear that you were able to get it working.
  7. Hi François, First, thanks for upgrading to Professional! That's a great suggestion and I'll pass it along to the VIPM developer team. In the meantime you might try the following: Keep all your polymorphic instances in a subfolder that is prefixed with an underscore (VIPM's auto-generated palettes will ignore all folders and VIs that whose name begins with an underscore). For example: \Filter 1D Array.vi \_Filter 1D Array\Filter 1D Array (DBL).vi \_Filter 1D Array\Filter 1D Array (String).vi \_Filter 1D Array\Filter 1D Array (Boolean).vi Would this work-around fit your development practices? Thanks, -Jim
  8. Hi, You can download the OpenG Packages, individually, here: http://sourceforge.net/projects/opengtoolkit/ There are also some links here: http://wiki.openg.org/Category:OpenG_Packages Once you have the packages, you can add them to VIPM's package list using the File>>Add Packages menu option. Thanks, -Jim
  9. I don't know if it's easy to detect the frontmost application/window. Do you know? Plus, I don't know if it's a good idea to add such a feature to VIPM, just to handle a situation where a build-hook *might* make itself frontmost. How does VIPM know that the reason VIPM is no longer frontmost is because of a build-hook? Maybe it's because the user clicked on another application to do some work while VIPM builds. As a short-term solution, I would suggest trying to have your build-hook make VIPM frontmost after the user interaction with your build-hook is finished.
  10. The way that I see it, there are two possibilities: 1) Don't pop open a dialog if the input path is empty. Keep the current behavior where the output "XML File Path (duplicate)" always equals the input "XML File Path". 2) Do pop open a dialog if the input path is empty. Change the input and output paths to "XML File Path (dialog if empty)" and "New XML File Path (Not A Path if canceled)". Option #2 seems like the easier solution for users. And, it doesn't really change the current behavior when an input path is empty. Plus, it is consistent with NI's high-level file utilities like "Read From Spreadsheet File" and "Write To Spreadsheet File". We'll discuss this more with the EasyXML development team.
  11. Hi Shabu, Here is a version that fixes this: Parse_Example_XML_2.vi Yes, the documentation for how to create the LabVIEW structures that map to XML data is here: http://jkisoft.com/easyxml/docs/#Detailed_Documentation Yes, I have a copy of your XML file. Can you be more specific about your requirements? The "Channel" field does not seem to be directly associated with the "" tag. How are you intending to traverse the data? Thanks, -Jim
  12. Hi Shabu, This can be a complex problem, because your data structure is highly compound and recursive. What I mean is that you have structure elements which can contain one or more field elements, which can contain structure, value, or collection elements. A collection contains one or more ordered value elements (with the order defined by the index attribute). The tricky part of this is that creating a tool for parsing this data in a generic way might be nearly as complex as the code under the hood of the EasyXML tool, itself (however, you might not need a generic parser, but a specific parser that expects files with certain fixed structure). What I mean, is this: The XML format that you're trying to parse seems to be a schema for storing arbitrary data from some other programming environment (or data storage system) -- it's not really an application-specific XML schema. For example, your XML format uses: instead of: 2428 Bottom line: your XML format is designed for storing arbitrary field names and types. Now, if you have a specific file or data structure that doesn't change, you can probably create a parser than can extract the data that you are looking for. For example, here is a VI that parses the XML that you posted (note that I had to add a trailing "" tag, in order to make the XML structure valid). Parse_Example_XML.vi What you'll then need to do is traverse this structure to find the fields with the names that you care about and then find the values of those fields. Let me know if this helps you out. Thanks, -Jim
  13. You shouldn't need the XSD file to extract the data in the XML file. Can you post your XML file? That would make helping you out a lot easier
  14. Thanks of reporting this. I can't reproduce the problem on my end. But, here's what I think you might be seeing: If you have several versions of a VI Package that VIPM knows about, when you right-click and choose Remove From Library, VIPM will only remove the latest version of the VI Package (which is the one being displayed). This leaves the previous version visible. So, you need to keep right-clicking and choosing Remove From Library until all known versions are gone. (unfortunately, there is no Remove All Versions From Library at this time). Does this sound like what you are seeing? If not, can you reproduce your issue? Thanks, -Jim
  15. Hi Richard, I haven't seen this problem. It sounds like an issue with the OS and the 8.0.1 run-time and 8.5 development environment installations. I don't have a test system with your configuration, so it will be hard for me to try to reproduce your issue. First, a few background questions: Did you install the 8.0.1 run-time engine before or after installing 8.5? Have you tried re-installing the run-time engine? Does it do this if you exit LabVIEW (so that LabVIEW 8.5 is not running) while you try to run vipm-1.0-linux? I hate to ask this, but have you tried contacting NI technical support? They might have seen this problem and know of a simple solution. Thanks, -Jim
  16. Hi bluesky, Putting UI event handling and work sequencing into separate while loops means that you cannot easily share statefulness between the two loops (using the shift register of state machine data). Generally, this statefulness is important when processing UI events. But, this does introduce the problem of work that takes a long time. There are a couple ways to deal with this: 1) Put the work somewhere else: maybe into another asynchronous while loop, as Omar suggested. 2) If you are building up a long sequence of work (multiple consecutive states), interleave some "Idle" states in there to service the Event Structure. Note that this requires that you have an Event Structure timeout other than -1 (Wait Forever) so that if there are no UI events your state machine will keep processing commands. In either case, you may want to implement some user interface interlocking (disabling of certain UI controls or all UI controls via setting the cursor to busy), which will lock out certain UI elements until the work is complete. We'll create some other examples, soon, that demonstrate how we recommend handling such things. Regarding your specific question about queues, one way that we can do this is to service a queue periodically inside the Event Structure's "Timeout" case, as shown below (note that this requires making sure that the Event Structure does not wait forever): But, as Omar also mentioned, at JKI we prefer to use User Events. We've got some interesting examples/templates that do this, too. Expect more exciting things to come! -Jim
  17. VIPM 2.0.2 has been released as a fix for some minor issues. Please see the VIPM 2.0.2 Release Notes page for more information. To download and install the latest version of VIPM, visit http://jkisoft.com/vipm/.
  18. Yes, I can see how having extra steps on the instructions would have helped. Those instructions do assume that you already know how to configure VIPM to talk to LabVIEW. I've added a final step that should help with this: This article points to the getting started information that shows (among other things) how to configure VIPM to communicate with your installed LabVIEW versions. Thanks again for all your feedback. I'm sure that this will help others, too.
  19. I see what you're saying. We do put some indications of this requirement in the configure port dialog that pops up when you select a LabVIEW version checkbox: Maybe we should add more documentation to the top of this dialog that says something like: "In order for VIPM to manage LabVIEW, it needs to communicate with LabVIEW's VI Server over TCP-IP. Please configure and test the TCP-IP Port, below. After you have adjusted and tested the settings, press OK to accept the settings." Would that help? Or, would you suggest something else? Thanks,
  20. I'm glad that you got it working. And, thanks for the feedback. I agree that the way the checkbox and configure LabVIEW Port dialog work together are too confusing. Thanks, -Jim
  21. Heiko, Yes, you can apply a package configuration with Community Edition. There are two ways to do this: In Windows File Explorer, right click on the VI Package Configuration file and choose Apply. Select File>>Apply a VI Package Configuration from VIPM's menu. Ideally, a Community Edition user would just double-click on a VI Package Configuration in Windows File Explorer to Apply it. This feature is scheduled for a future release. Thanks, -Jim
  22. Thanks for reporting this. I haven't seen or heard of this problem, but this information will be very useful should the issue start appearing again for you or others.
  23. When you get back into work, can you please take a screenshot of VIPM on your non-networked computer that shows the disabled menu items (that are preventing you from doing step #4)? Thanks,
  24. Which VIPM version are you using (this can be found in the Help>About window)? I want to make sure that I'm testing with the same version as you. Also, adding and selecting LabVIEW versions should not require connecting to the Internet. Is the LabVIEW Version selector grayed out? And, the File>>Add Package(s) menu should not be disabled. I'll try to do some more testing to see if I can reproduce your problem.
  25. Hi, Where are you getting stuck? What's the last action that you are taking? What are you seeing and what did you expect to happen? When I select File>>Add Package(s), I see the following dialog: When you select packages and press Add, they should appear in your package list. If you don't see anything, make sure that you have selected a LabVIEW version selected: If no LabVIEW versions are available, make sure that you've configured your LabVIEW versions in the Options dialog. Let me know if this helps or if you still have questions. Thanks, -Jim
  • Create New...

Important Information

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