Jump to content

Jim Kring

JKI Team
  • Content Count

    1,688
  • Joined

  • Last visited

  • Days Won

    40

Everything posted by Jim Kring

  1. I'm glad you got it working and thanks for the kind words. Also, if you attach your VI, I can help you get it working with the XML structure in your first example -- I'm very curious why it wasn't working. We're looking forward to having you as a customer. Good luck with your project. -Jim
  2. This links appear to not be working well this morning. Here is a link to the page where you can choose alternate mirror locations: * ogrsc_dynamicpalette-0.18-1.ogp * ogrsc_builder-2.0.0.399-1.ogp * oglib_numeric-2.3-2.ogp
  3. Hi Frank, You can download the required packages from these links: * ogrsc_dynamicpalette-0.18-1.ogp * ogrsc_builder-2.0.0.399-1.ogp * oglib_numeric-2.3-2.ogp Please let me know if this works for you
  4. Hi, I think you're almost there! What I see is that you probably need to rename your "items" array as "item" and then put that "item" array inside a cluster called "items". Note that you structured the "groups" cluster and "group" array correctly. Please let me know if that helps. Thanks, -Jim
  5. Hi Yen, This is a known issue. Basically, if the RCF is running and has "development/source" plugins loaded, VIPM will not be able to build your package. The way to work around this is to either stop the RCF or to disable loading of source plugins by setting your plugin development source path to empty path. Note, I've file a feature request to add a checkbox to enable/disable all source plugins in the options dialog: Case 7778: "Enable/Disable source plugins checkbox on options dialog"
  6. Hi Yair, Please run OpenG Builder from the LabVIEW Tools>>OpenG Builder... menu. It should tell you that it needs to mass-compile itself. Let it do this, then restart LabVIEW. This should fix the issue. Please let me know if it does. Thanks,
  7. Hi Marc, I see your points and agree that they are valid. And, I can see how you might want to installer your libraries and have the underlying installer framework (VIPM, in this case) being more silent/hidden. Thanks, -Jim
  8. Hi Marc, Can you explain a little more about what you'd like to see VIPM do here? VIPM can scan folders to see which packages (that are currently installed) are being used (in the Package Configuration Edtor window). It let's you use this information to create and manage a VI Package Configuration (.vipc) file. When you open the VIPC file, you can easily see which packages have newer versions available (they have a star overlay on the package glyph). Thanks, -Jim
  9. Hi Marc, Thanks for the great feedback. I'm happy to hear that you're building a lot of packages! This is something that we're currently evaluating internally at JKI. You might notice that JKI delivers some of its own packages in both demo and paid versions. We have internal tools for doing this, but they're not part of the product. When we get to a point where we're ready to start testing, we'll be sure to let you know -- we'd love to have your feedback. Thanks, -Jim
  10. Hi Marc, Thanks for the suggestion. The feature you describe is not currently on our road map due to the limited number of users who would benefit from it (in our opinion) and the high degree to technical complexity. Regarding your use cases: 1) If a user is not allowed to install VIPM, why would they be allowed to install just a single package? (assuming that installing a package required it to be an EXE) 2) If users don't want to install VIPM, we (JKI) want to know why so that we can address those problems. What issues/hesitations do you see? Thanks, -Jim
  11. Hi Marshal, I'm glad you were able to get it going on mac intel. Yes, from what I recall, we decided to wait for 2.0 to bring back support for Mac. It's sometimes a major effort to get everything working and building correctly. Thanks, -Jim
  12. Hi Marc, Here's a post-build hook VI that should work for your custom probe package. It will remove the underscore from the LLB file inside the package. This is a bit of a hack, but it should work for you. Thanks, -Jim Remove_Underscore_from_LLB_Name_in_VI_Package.vi
  13. Hi Marshal One of our engineers (Omar Mussa, who just replied to this thread) has confirmed that VIPM 2.0 won't install on Mac PPC. And, I'm not sure if there's anything we can do about that, since this seems to be a LabVIEW issue. Note: you should not do any mass compiling with the LabVIEW Development environment, nor should you do anything to the LLBs inside the .app files. This is a "built" application and it will only run with the LabVIEW run-time engine. Nothing you do in the LabVIEW Development environment can fix the issue, since the VIs inside the LLB inside the .app have no block diagrams. Also, I'm pretty sure that if you download the Mac installer from our website and install it on Mac Intel, it should work. Please don't try installing anything that you've already attempted to mass compile using LabVIEW. The .app might have become corrupt. Thanks, -Jim
  14. Hi Marshal, I'm not sure what's causing this issue. Did the VIPM installer run OK? Is this just an issue with the "VI Package Manager.app"? Also, I think that VIPM 2.0 might only work on Mac Intel. We haven't done any testing on PPC. Yes, you're right that many of the newer packages will not install using VIPM 1.0. Thanks, -Jim
  15. Hi Danny, The license agreement is here. Please let me know if you have any questions or concerns. Thanks, -Jim
  16. I got your email. I've sent you some more debugging steps. Thanks for your help!
  17. Hi Mike, Please check your email. I've sent you some details on how to help debug the issue. Thanks, -Jim
  18. Hi Shaun, I just did a quick test and it's not working the way that I thought it might. TSVN moves/renames the file to the new directory, but LabVIEW doesn't know that the file has moved to a new location. In this case, after you rename the file with TSVN, you should do a Save As in LabVIEW an select the new location in the file dialog. Thanks, -Jim
  19. Hi Marc, Thanks for posting this. I'll take a look and get back to you, shortly. Thanks, -Jim
  20. Hi Mike, I've passed your bug report on to our development team to see if they have any ideas. I'll report back, shortly. Thanks,
  21. Hi Shaun, I'm pretty sure that you can move a file in the TSVN rename dialog. For example, to move /Project/FolderA/File1.vi to /Project/FolderB/File1.vi, simply enter ../FolderB/File1.vi as the new name. Now, I'm not sure, off-hand, whether the JKI TSVN Tool will handle this gracefully -- I'm about 75% confident. Please try and let me know Thanks, -Jim
  22. Hi Maze, I'm pretty sure that the problem you're seeing is a known issue (Case 5788). I've emailed you some information and will help try to get you up and running. Thanks, -Jim
  23. Hi Bob, Great! Now, you're all ready to work over the holiday weekend Cheers, -Jim
  24. Hi Bob, Thanks for all the info. Again, I'm so sorry to hear that you've had to do so much re-installing trying to get this working. Can you please do the following? 1) In VIPM, check the network for package updates to ensure that VIPM knows about all the latest packages that are available. You can do this by selecting 2) In VIPM, uninstall EasyXML and then re-install it Now, try opening your project. My suspicion is that you uninstalled LabVIEW and removed some previously installed packages. The preferred operation for uninstalling LabVIEW is to first uninstall all packages in VIPM and then uninstall LabVIEW. Otherwise, VIPM doesn't know that you've deleted installed package VIs when you uninstalled LabVIEW. Please let me know if this helps. Thanks, -Jim
  25. I'm glad to hear that you found the issue and that it was a simple fix. I'm not sure if this relates to your issue, but I usually always set cluster Autosizing to Arrange Vertically (or Horizontally), so that the cluster element order is obvious.
×
×
  • Create New...

Important Information

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