Jump to content

tyk007

Members
  • Content Count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. I ended up solving the issue by manually opening the control of each class, making an insignificant change (such as re-sizing the cluster) and then applying changes to the control. Although no methods VIs changed this seemed to allow VIPM to perform the build.
  2. I have a vip configuration for a project that uses a number of labview classes. Recently I renamed some of the classes for various reasons. The source mass compiles fine in LabVIEW 2012 (after clearing the compiled object cache). During the VIPM build, I get Error Code 7. Virtually every file in the build is now "missing dependencies" - yet when I open the project in LabVIEW the offending VIs are ok - no broken run arrows etc. I also get this wierd error message: The file at 'D:\xxxxxxx\.Source2012\VariantTools\VariantTools-GUnit.lvclass\VariantTools-GUnit.ctl' was expected to have the qualified name 'VariantTools-GUnit.lvclass:VariantTools-GUnit.ctl', but has the qualified name 'VariantTools.lvclass:VariantTools-GUnit.ctl'. Not sure why this error exists. THe class file opens fine in LabVIEW 2012, and looking at the xml indicates the ctl file name is correct. Any ideas?
  3. This behaviour is also incorrect in LabVIEW 2013 and requires manual tweaking of the method VIs to get around it for every TestCase child class. With any luck there might be an update at some point to correct the class generation code.
  4. I would love to make more use out of VI Tester, but since I'm using LabVIEW 2012 and 2013, the TestCase-From-Template bug that has been posted on the forums by shb causes us a lot of grief making it significantly more awkward to use than NI's UTF. Is there any news on when any updates might be made? Or (dare I ask) the possibility of opening up the VIs to allow the community to make these modest improvements?
×
×
  • Create New...

Important Information

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