Jump to content

Ashish

JKI Team
  • Content Count

    293
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by Ashish

  1. JG, Thanks for sharing your observations. It does help to improve our product quality. I was able to reproduce the behavior and filed Case 13110 for us at JKI to manage the issue for future VIPM release. Feel free to share any additional information related to this issue. Thank you.
  2. judomagyar, Thanks for testing this at home since that is how we have really isolate the problem most of the times. I would recommend login as an administrator while installing VIPM and packages. Some clarification: - VIPM 2011.0.1 has a bug where it hangs while installing certain packages with status (at the bottom of the window) displaying "resolving dependencies" This should not happen in VIPM 2011.0.0. So, if your VIPM 2011.0.0 hangs, please provide us with additional information/screenshot to help us investigate. Thank you.
  3. Brian, What you need is a "Subpanel" to display Front Panel of a VI (running independently) in another VI. Here is a link to an article on NI website describing the implementation of subpanel: http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/loading_panel_in_subpanel/ You do not have to make SubVI of one State Machine VI into another, but run them in parallel and independent and use Sub Panel to display front panel of one VI into front panel of another VI. Hope this helps.
  4. judomagyar, Thanks for your feedback. Are you saying that both the VIPM versions (2011.0.0 and 2011.0.1) hanged while installing the "MGI read/write anything" package?
  5. Kris, I was able to reproduce the issue using IE8. The PC had nothing related to LabVIEW or VIPM on it. The issues is caused dure to security settings in IE8 which identifies unknown file type (in this case, ".vip" file) and renames it to ".zip". i was able to disable this "feature" of IE8 by changing the security setting in IE8 to "Medium". Here is a video demonstrating the issue and the solution to fix the problem: http://screencast.com/t/MqiXFn9EfSb - Ashish
  6. Lee, You've experienced a bug in the VIPM 2011.0.1's dependency resolution. It probably only affects a small number of packages, but unfortunately “Structured Error Handler” is one of them. We have reproduced the bug and are working on a fix, but I don't have a timetable for when it will be ready. In the meantime, the only workaround I can give you is to downgrade back to VIPM 2011.0.0. Here is the link to download the old installer: http://jkisoft.com/updates/vipm-2011-windows-setup.exe I apologize again for the trouble, and I hope downgrading (for now) isn't a huge hassle for you. If you need anything else please post back and we'll be glad to help. Thank you. - Ashish
  7. Pat, Glad to know that you managed to build a new package. We will certainly look into possible reason for the issue you experienced. VI Package Icon Editor is part of the community edition of VIPM!! Here is the link to the comparison chart: http://jki.net/vipm/compare Here is link to an article describing on how to modify the package icon: http://support.jki.net/entries/20654736-editing-the-package-icon I will also recommend you to read this thread specifically for VI Package Icon Editor and labVIEW 2011: http://forums.jki.net/topic/1717-icon-editor-deletes-current-icon-and-prevents-future-edits-of-new-icon/ - Ashish
  8. Norm, Thanks for reporting the issue and the video description to demonstrate the issue. We were able to re-create the issue and it does seem to be a bug in VI Package Builder while using LabVIEW 2011 Icon Editor. The issues has been logged as Case 13057 and will be addressed in the next bug release. - Ashish
  9. Sorry for the problem, The JKI TortoiseSVN tool does not currently support TortoiseSVN 1.7.1. Please downgrade to version 1.6 or earlier. We are currently working on a patch release to address this issue. It should be released around November 15th, at the earliest.
  10. Hi, I had to transfer the EasyXML License to another PC. So, I uninstalled it from old PC using VIPM. And then, I installed EasyXML on the new PC....again using VIPM. Is there anything else I need to do? Thank you/ - Ashish
×
×
  • Create New...

Important Information

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