jgcode Posted April 26, 2011 Report Share Posted April 26, 2011 VIPM 2010.0.2 Steps to reproduce the bug (if it can be reproduced) Create a Package (e.g. Test Package) which links to a VI in another package (OpenG File IO), and where that VI links to another VI in a different package (OpenG Error) Build your Package (Test Package) so that it has no external dependencies i.e. VIPM will automatically add and rename all VI dependencies to your package internally. The VIPC file shows all dependencies. Only the File IO VI is called directly by my VI. I do not include any dependencies. I want all calling VIs to be included as internal dependencies. Expected behavior (what would happen if the bug didn't exist) Test Package has no dependencies. Actual, observed behavior (the bug) Test Package has OpenG Error dependency. I uninstall the OpenG Error Package, then load my VI to show the dependency exists. Additionally, only File IO VIs are included in the _internal_deps dist folder (<vi.lib>\JGCODE\_Test Package_internal_deps). The VI is installed in its own palette using a Custom Category for easy testing. I have attached the Package code for testing. Test Package.zip Code is in LabVIEW 2009 Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted April 26, 2011 Report Share Posted April 26, 2011 Thanks for the detailed bug report. I've tracked it as case#11500 Link to comment Share on other sites More sharing options...
jgcode Posted April 27, 2011 Author Report Share Posted April 27, 2011 Thanks for the detailed bug report. You're welcome Edit: plus you will be happy to note I refrained from the [] prefixes in my thread titles Link to comment Share on other sites More sharing options...
Jim Kring Posted April 28, 2011 Report Share Posted April 28, 2011 Yep, I think it's a bug! Link to comment Share on other sites More sharing options...
jgcode Posted August 3, 2011 Author Report Share Posted August 3, 2011 Hi Guys, congrats on VIPM 2011 - can't wait to try it. Has this bug been fixed in this version? Cheers -JG Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted August 8, 2011 Report Share Posted August 8, 2011 Hi Guys, congrats on VIPM 2011 - can't wait to try it. Has this bug been fixed in this version? Cheers -JG Sorry, this has not been fixed in VIPM 2011. We are planning an upcoming release to address a host of issues including this one. Link to comment Share on other sites More sharing options...
jgcode Posted August 11, 2011 Author Report Share Posted August 11, 2011 Sorry, this has not been fixed in VIPM 2011. We are planning an upcoming release to address a host of issues including this one. Cool. That's great. Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted April 9, 2012 Report Share Posted April 9, 2012 Just want to confirm that this issue is fixed in the latest version of VIPM. Link to comment Share on other sites More sharing options...
jgcode Posted April 11, 2012 Author Report Share Posted April 11, 2012 Awesome - thanks for the update. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.