Jump to content

Ravens Fan

Members
  • Content Count

    1
  • Joined

  • Last visited

Community Reputation

0

About Ravens Fan

  • Rank
    One hit wonder!

Profile Information

  • Gender
    Not Telling

LabVIEW Information

  • Version
    LabVIEW 2013
  • Since
    2005
  1. I've had issues with this as well. I'm hoping it can be fixed, because it just doesn't make sense. I think I've been battling it for a couple years, but got by with just copying the appropriate files from the old PC to the new. I failed to do that when I got my new laptop a couple weeks ago, and I'm trying to install it fresh. I installed VIPM, then allowed it to update itself. I try to install the CCT that shows up automatically and appears to be the latest version 3.2.1-46. It says I can't because it conflicts with the Code_Capture_Tool 0.0.1 which I don't have installed at all because this is a fresh PCl, fresh LabVIEW, and fresh VIPM setup. I was able to find an old .OGP file I had on my PC from 4 years ago, version 2.1.4-1. It installed without any issues. Then I was able to install the new 3.2.1-46. It says there is an auto-conflict with 2.1.4-1 and it will uninstall the old version. It uninstalls the old version and installs the new without any errors. However, the VIPM screen shows a warning icon for the new CCT. But the CCT seems to work just fine in LabVIEW. I think it is related to the conflict with the Code_Capture_Tool 0.0.1, but the conflict is backwards and actually does install more or less properly when you do have an old version with underscores, but fails to install if you don't have an old version of the CCT installed. The CCT is by far superior to the built-in LabVIEW snippet tool. I use it all the time and recommend it to others. But the conflict issue on install is a huge barrier when it really shouldn't be. And as time moves on, the chances of someone having the old CCT, and a real conflict with the old CCT should be very infrequent.
×
×
  • Create New...

Important Information

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