Jump to content

Jim Kring

JKI Team
  • Content Count

    1,364
  • Joined

  • Last visited

  • Days Won

    17

Everything posted by Jim Kring

  1. Would just putting "VIPM 2011" (including version) in the User-Agent header field be sufficient?
  2. Hey Jason, Here is a manual work-around, that will should fix the toolbar issue in 2011. VITester.ini.zip Place the attached VITester.ini file in the following location: \resource\Framework\Providers\GProviders\VITester.ini Hopefully, that'll do the trick. Let us know. -Jim
  3. Hi Brad, I'm glad you got this working. We'll be working on a fix for a future version of VIPM. Sorry for the trouble. -Jim
  4. Hi Brad, Sorry for the trouble. I think there is a bug that is causing VIPM to think that the 4.x versions of the OpenG libraries can be installed onto LabVIEW 8.6. However, the 4.x versions of the OpenG libraries require LabVIEW 2009 or greater. To resolve these issues, you should try to manually install the 3.x versions. To do this, open the Main VIPM Package List and type "OpenG" into the searchbox. Make sure that you have LabVIEW 8.6 selected in the LabVIEW version selector drop-down. Then find the packages you want from the list -- select all the "OpenG" ones and then click the Install toolbar button. Please let me know if that works -- on our side, we'll look into a fix for this issue.
  5. Winner, winner, chicken dinner!
  6. Hey Dan, What are the requirements (in terms of XML data structure) of an Excel XML Table? Also, there are a few ways to represent ordered arrays of data. Here's one way to do it (using an attribute to store the station number): 1 2 3 If you really want to use the exact XML schema you showed, then you'll need to use a Variant representation of your cluster and construct its elements and their names dynamically (e.g. using the OpenG LabVIEW Data Tools library for variant manipulation). -Jim
  7. Hi Kim, There is a bug in the dependency declaration of the LabPython package. It should declare a dependency on ogrsc_dynamicpalette ">= 0.2" instead of ">= 2.0". Go ahead and install version 0.19 of ogrsc_dynamicpalette and everything should be fine Thanks, -Jim
  8. Hi bananacluster, 1) I can send you a copy of the demo version that works with Windows 64-bit. Please contact us and we'll email you a link. 2) You need to install TortoiseSVN first. 3) The JKI TortoiseSVN Tool is not a LabVIEW Source Code Control Provider plugin -- it adds items to the Tools>> menu. You can watch a short video to see how it works, here: http://jki.net/tortoisesvn-tool Thanks, -Jim
  9. Jim Kring

    Loading Tests

    Hey Dan, My suspicion is that tests inside of auto-populating folders are not being found by VI Tester. Can you try adding them to a "regular" project folder? Thanks, -Jim
  10. Hi, Are you married to the schema designed by your colleague in Pearl? IMO, it's pretty difficult to deal with, in the case where you want scalability of the number of bits. For example, it would be hard to validate it using a XSD or DTD.One solution might be to use attributes, like this: <REGPGMS> <name>R0</name> <bit i="0">0</bit> <bit i="1">1</bit> <bit i="2">1</bit> <bit i="3">1</bit> <bit i="4">0</bit> <bit i="5">1</bit> <bit i="6">0</bit> <bit i="7">1</bit> </REGPGMS> Thanks, -Jim
  11. Hi Eric, Thanks for posting these! I'll ping others at JKI to take a look. -Jim
  12. OK, I see. It's good to hear that this is just a one time thing, while you migrate over to using VIPM to build your packages. We've looked into the possibility of having an "importer" for existing MNU files, but it's a little bit tricky. Ya, copying the icon of existing palette MNU files within LabVIEW is a bit of a hassle -- I'll mention this to the VIPM dev team and we'll think about ways we can improve this, in the future. Thanks!
  13. I see -- so, this issue really only impacts you once, when you're migrating from your old palette MNUs to using VIPM to create packages. Is that right? Or, are you going to need to resync these palette icons again, from the source location into VIPM?
  14. Once you have the VI Tester window open, try selecting File >> Open Project of Test Class and then browse to your project (.lvproj) or test case/suite (.lvclass) file. Does that work for you?
  15. There's no way to do this, currently. Can you describe a little more about your use case? Do you already have icons defined somewhere else? Or, do you use some icon editor outside LabVIEW? Or, is this just for the first time you create icons? Thanks!
  16. Cool. I'm glad this works for you. I'm happy to help.
  17. For the case you mentioned, I would create a "Comparison" package and have it install into the RFI custom category, as shown below: Does this do what you want? Try building and installing your package this way and let me know if it works. Thanks, -Jim
  18. Hi There. This thread is really only relevant for VIPM 3.0. In VIPM 2010, we added the ability to create/install a custom palette category for your package. Have you tried this? Can you explain more about what you are trying to accomplish, so that we can best help you? Thanks!
  19. Hi, Sorry for the trouble. Do any of the debugging tips in this other thread help? Thanks, -Jim
  20. There are a couple routes: You could download and install them at home and then copy the VIs from user.lib, etc. and move them onto your work computer via sneakernet. Another option would be to download all the sources from sourceforge: http://sourceforge.net/projects/opengtoolkit/ Both of these methods will be difficult, which is why we made VIPM
  21. Great! I'm glad that worked for you. Thanks for letting us know. -Jim
  22. Hi Gavin, Thanks for reporting this. Would you be willing to work with us to help get this resolved? We can try to fix and then have you test. Cheers, -Jim
  23. Hi Ed, Sorry for the trouble. We've got a fix for this. We'll follow up with you off-line, right away. -Jim
×
×
  • Create New...

Important Information

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