03-31-2016 04:59 PM
Such good discussion on such a great tool. LabVIEW really needs custom shortcut menus for tools menu items. Then you could do CTRL+a, and CTRL+/ to launch CCT. Since it remembers your settings, as others have said I usually just press the one button that makes the snippet, saves in in the temp folder, and copies the path to my clipboard. Then when I'm on the forums I just past the path to the image to upload, no file browsing, which is another bonus it has over the built in tool.
Yeah the UI isn't perfect, but I've never found a reason to complain. I did find it created an unhandled error and stopped if I messed around with zooming, panning, and resizing the window too much. But I'd never have even used it until this discussion came up and all the sudden I wanted to click all the things.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
04-01-2016 04:01 PM - edited 04-01-2016 04:02 PM
I haven't been very active on the forums the last few years so I haven't needed to make many screenshots. This thread made me realize I don't even have the CCT installed on my current computer. Anyone know what to do here?
04-01-2016 04:19 PM - edited 04-01-2016 04:21 PM
Yeah update your VIPM, and your CCT, there was an issue where you needed VIPM 2014, and there was a bug where a version of the CCT was incompatibile with itself somehow.
https://lavag.org/topic/10309-lvtn-code-capture-tool/page-3
Notice how in your screenshot it actually says it can't be installed with CCT > 0.0.1, kinda odd since you are trying to install a newer verion than that right?
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
04-01-2016 04:51 PM
I ran into the same problem this morning. I ended up here https://lavag.org/files/go/4d7cac4318954fa5a1df1a66f76a1eda/code-capture-tool and selected the 3.2.3-51 file and it worked. I already had the latest VIPM and only the -51 file worked. On my machine connected to the internet it worked fine. The fun part came when I installed it on a machine not connected to the internet. I had to manually find the LAVA palette on the FTP and move it to the machine with a thumb drive. But everything seems to be working now.
04-01-2016 05:40 PM - edited 04-01-2016 05:48 PM
Edit: wrong link in that but Hoovahh is in the right area
from LAVA Re failed CCT installs:
"Resolved by downloading CCT 2.1.3-1 and installing that package first from the product homepage. VIPM was scessful in installing 3.2.1-46 as an upgrade"
04-04-2016 07:34 AM
Yeah I couldn't remember exactly what version of what worked, but I knew the thread discussed it, and a solution is in there somewhere.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord