Jump to content

OllyT

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral
  1. Anyone have any insight into this problem? It's becoming quite an issue for me now. Thanks.
  2. Probably should have said, I am running VIPM 2014 with Win 7 Pro 32-bit. The code I am trying to package is a simple folder of VIs. No projects, libraries or classes.
  3. To get around an issue I'm having (http://forums.jki.net/topic/2635-all-source-files-must-be-closed/) I need to check the "Do Not Compile On Build (Not Recommended)" check box for some files. When I do this however, VIPM creates two copies of the file when it installs the package. One which preserves the folder structure of where it was packaged from and one which is just chucked in the top directory of the installed package folder. Having two copies of the files in the vi.liv directory is then causing me to have "conflicts" I need to resolve. Am I doing something incorrectly or is this a bug with VIPM? Thanks for any help.
  4. Sorry for the double post, my browser seems to hang when you hit the "post" button and doesn't show a success message.
  5. I'm encountering an error when trying to build a package with VIPM 2014. VIPM will report that "In order to build your VI Package, all source files (for example, VIs or CTLs) must be closed within LabVIEW. Please review the following VI list and make sure they are closed. Note: If you continue to see this message, you may have some VI Package source files on your (Copy/Paste) clipboard or they are [sic] may be called by other VIs that are open in LabVIEW". I have tried completely shutting LabVIEW down. Rebooting the PC. Clearing the clipboard. Checking the files will run and have all required dependencies and now I'm completely out of ideas? I'm getting quite a few files doing this and I can't seem to determine what is different with these files to others. I can get the package to build if I select "Do not compile on build" but this isn't particularly ideal. It is also causing some other issues I will post in a new topic. VIPM 2014 Win 7 Pro 32 bit Any thoughts/ideas? Thanks
  6. I'm encountering an error when trying to build a package with VIPM 2014. VIPM will report that "In order to build your VI Package, all source files (for example, VIs or CTLs) must be closed within LabVIEW. Please review the following VI list and make sure they are closed. Note: If you continue to see this message, you may have some VI Package source files on your (Copy/Paste) clipboard or they are [sic] may be called by other VIs that are open in LabVIEW". I have tried completely shutting LabVIEW down. Rebooting the PC. Clearing the clipboard. Checking the files will run and have all required dependencies and now I'm completely out of ideas? I'm getting quite a few files doing this and I can't seem to determine what is different with these files to others. I can get the package to build if I select "Do not compile on build" but this isn't particularly ideal. It is also causing some other issues I will post in a new topic. VIPM 2014 Win 7 Pro 32 bit Any thoughts/ideas? Thanks
  7. Hi All, I'm encountering an error trying to build a package in VIPM (2013 Pro). I'm pretty sure I've cause this problem myself, but can't quite put my finger on exactly what is wrong... Firstly I'll give you a brief bit of (probably relevant) background info. I am using LabVIEW 2012 SP1 and for various reasons I needed/wanted to branch off development of a few LVOOP classes that a supplier has provided. So I took the (probably unadvisable) step of saving the classes with different names. This seemed to work fine and I encountered few problems doing so (other than having to make sure the classes had the correct version of VIs inside them and not ones from the old class). Next I created a brand new class (Power Supply Class) and had it inherit from my new classes. Everything still seems to work fine and it all runs ok. So My new class structure is something along the lines of: CDE Root ->CDE SCPI Instrument (child of CDE Root) --->Power Supply Class (child of CDE SCPI Instrument) Both the root and SCPI classes packaged up fine. However whenever I try to build the Power Supply Class I get the following error: So, Information.ctl is a control that exists in CDE SCPI Instrument but not in the Power Supply Class (it is just used there). Can anyone shed any light on how I might go about resolving this? I've tried the usual stuff of shutting LabVIEW down, rebooting windows but no joy! Thanks, Olly
×

Important Information

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