Jump to content

Jim Kring

JKI Team
  • Content Count

    1,365
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by Jim Kring

  1. To close off this issue, Jason and I did some trouble-shooting off-line. Reinstalling EasyXML and dependency packages fixed the Error 1 problem.
  2. Just a quick comment: jki_lib_easyxml-1.0-1 is the demo version jki_lib_easyxml-1.0-2 is the paid version We use this scheme, so that the paid version is always an upgrade to the demo version. -Jim
  3. OK, keep us posted. Also, I'll try to push the fix for the OpenG issue though quickly.
  4. Jason, That's a great addition to the set of examples. Thanks for providing that. I'll update the example, shortly. FYI, we're planning to add this VI to the shipping examples located at "\examples\JKI\EasyXML". Thanks again, -Jim
  5. Hi Jason, Sorry to hear you're having trouble -- FYI, in a future version, we're planning to improve the error messages to provide better info about which data elements are causing the issues. Regarding your example, it seems to work OK for me. Please, see the screenshot, below: Also, which versions of the LabVIEW and OpenG/JKI packages are you using? Here's what I'm testing with: LabVIEW 8.5.1 ogrsc_dynamicpalette-0.16-1 oglib_string-2.6-1 oglib_lvdata-2.8-1 oglib_error-2.3-2 oglib_array-2.7-1 nirsc_html_help_common-2.0-1 jki_rsc_toolkits_palette-1.1-1 jki_lib_easyxml-1.0-2 Thanks, -Jim PS - I deleted and replaced your attachment, since it had some default XML string data that didn't match your example data structure.
  6. Hello Geir, Thanks for the feedback. We're happy that you like EasyXML I have reproduced the problem and have created a case and known issue topic in the forums, here: Known Issue (Case 5206): International characters in names should not be removed We appreciate you reporting this issue and will try to get it fixed as soon as possible. If you need a fix sooner and would like to help us test the next release, please send us a message via our contact form. Thanks, -Jim Kring
  7. Versions Affected: 1.0 Fixed in: Pending International characters in element and attribute names should not be removed. For example, "æ ø å" is being converted to "__" instead of "æ_ø_å". This was first reported, here.
  8. Hi Jason, Thanks for the great feedback. First, we're considering adding a feature that will allow you to override the default formatting for floating points. I agree that you often need more control over precision/significant figures. Second, I agree that using significant digits is superior to precision and that it would be helpful to include more digits by default. We'll certainly consider changing the default in a future release. Thanks, -Jim
  9. Hi Travis, It's going very well. We can't make any commitments as to when we will publicly release a new version. That said, if you would like to help us test out some of these improvements, please send us a message via our contact form. We appreciate your feedback and efforts as an early adoptor Thanks, -Jim
  10. Hi Ton, Thanks for the update. That's good news. I've added a brief comment about this, in the FAQ: How do I configure VIPM to use a proxy server? Thanks, -Jim
  11. Hi Jason, Thanks for the feedback. I have updated the FAQ: Can I install VIPM on Windows Vista? I'm glad to hear that you were able to get it working Thank you, -Jim
  12. Thanks for the update. That's great to hear. -Jim
  13. Hi Jed, You're really putting EasyXML through the paces We appreciate you reporting these issues and will try to get these fixed as soon as possible. I have reproduced the problem and have created a case and known issue topic in the forums, here: Known Issue (Case 5175): Colon characters in names should not be removed Thanks again, -Jim
  14. Versions Affected: 1.0 Fixed in: Pending Colon characters in names should not be removed. For example, "xml:value" is being converted to "xmlvalue" This was first reported, here.
  15. I have just created a Known Issues entry, here: Known Issue (Case 5174): Attributes with single quotes aren't working
  16. Versions Affected: 1.0 Fixed in: Pending Attributes should work with either single or double quotes. Currently, single quotes are not working -- only double quotes work. This was first reported, here.
  17. Hi Jed, Thanks for reporting this. I can reproduce the problem on my end and have created a case (5174: Attributes with single quotes aren't working) in our issue tracking system. I'm not sure about the Google API spec. Thanks, -Jim
  18. Hi Travis, VIPM 1.0 does not work with LabVIEW 8.5, which is what you're seeing. Support for VIPM 1.1 on Macs has been held up, due to some MacIntel complications, but we're working on it and hopefully it won't take too much longer. If you are in a real bind about how to get EasyXML working on Mac, there are options. Probably, the easiest is to copy the installed EasyXML and OpenG files from another version of LabVIEW (possibly on another computer) that VIPM is able to target, located here: \user.lib\_OpenG.lib\* \vi.lib\addons\_JKI Toolkits\* Also, if you need the OpenG and JKI Toolkit palette categories, copy the mnu files located here: \menus\Categories\OpenG.mnu \menus\Categories\JKI Toolkits.mnu We appologize for this inconvenience. Please let us know if you have further questions about getting EasyXML working on your Mac. We're committed to getting a temporary fix working for you, now, and getting VIPM 1.1 working, as soon as we can. Thanks, -Jim
  19. Hi Travis, [Disclaimer] I'm not a lawyer, so please don't take this as legal advice and make sure to consult with your attorney about any license compliance issues [/Disclaimer] When you build an application that uses EasyXML, you need to comply with (1) the JKI Toolkits Full Version License, (2) the license agreement of the OpenG VIs that EasyXML depends upon, (3) the LabVIEW license agreement, and (4) the license agreements of any other third party that you are using. Regarding #1 (EasyXML), Section 1.3 of the JKI Toolkits Full Version License states the following: ...the Customer Product will include in its About Box or other applicable written documentation the notice that the Customer Product "includes the JKI Toolkits for LabVIEW, © (year) JKI. All rights reserved." Regarding #2 (OpenG), take a look at the How do I comply with the BSD license? FAQ on the OpenG website. Regarding #3 (LabVIEW), section 13.A.1 of the NI General Purpose Software License Agreement states the following: ...include the following copyright notice "Copyright © [yr] National Instruments Corporation. All Rights Reserved" in the Authorized Application's About Box and in the applicable written documentation distributed with each copy of the Authorized Application... Regarding #4 (other 3rd party software), you'll need to check into the details of these, yourself, of course. I hope this info helps and I'm sorry if my response seems like I don't want to directly answer your question. We have to be very careful to not give legal advice, since that's not our expertise. Thanks, -Jim
  20. That thought crossed my mind, too. We'll look into whether this is feasible. Thanks, -Jim
  21. Hi Travis, Here's a another quick update: We've made several optimizations and have gotten the time to execute your TCX read test case down to under 8 seconds (in LabVIEW 8.5 using the same machine that produced the stats in my previous post). The good news is also that the divide and conquer approach is only slightly faster (about 500ms). Please don't take this as a promise or guarantee that we'll have a new, better-performing version out immediately, but I wanted to let you know that we are working hard on this issue and think we have a good solution. That said, we still need to do a lot of testing and some more fine-tuning -- this was a significant over-haul of the code. Thanks, -Jim
  22. I'm glad it's working for you now. Thanks for posting your solution, just in case others see this problem, too.
  23. That's great news. Let us know if you have any other issues or feedback. Thanks, -Jim
  24. Travis, Thank you for your vote of confidence. We'll certainly work hard to keep improving EasyXML, and keep you as a happy customer Regarding the licensing, it is a per-user license with no restrictions on the number of applications or computers on which it can be installed. We just ask that you have one license for each developer who is using EasyXML to create software. Thanks, -Jim
  25. Travis, Here's a quick update... We've started doing some work to try to optimize the code, including rewriting the XML string parser, changing the data traversal routine from VI recursion to loop-stack and also looking into ways to improve the variant handling and parsing of the LabVIEW data+type descriptors. None of this work is trivial and will take a little time to get right. But, we're committed to getting EasyXML to perform to its full potential. We might not have an immediate solution to your large XML file issue, but we're working hard on it. Thanks, -Jim
×
×
  • Create New...

Important Information

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