Clicker

This could be because you have a VISA control within your class data. I found this to be a problem when converting from 8.2 to 8.5. Please refer to: http://forums.lavag.org/85-LVOOP-Upgrade-Problem-t8795.html

Well when I said 8.2 I meant 8.2.1. But anyhow, yeah thanks for this work around. So if you don't mind me asking why do you need to edit the control? Does this replace the older control with a newer one? QUOTE(Aristos Queue @ Aug 10 2007, 02:58 PM) I don't have a CAR number but I do have a reference number: 7165459. I'm not sure if that is the same or not.

I do thank you for taking a look at this in more detail. I also thought it could just be a file corruption or something along thoses lines so I did a few 'experiments' to determine it was the VISA control after it was converted and saved in 8.5. One of those was to create a new class from scratch containing the VISA control itself in 8.2 and then update it to 8.5, after resaving it and attempting to close/open it had the same issue. Then I used that same class created in 8.2 and just replaced the VISA control with a string control everything worked nicely. So based on that it leads me to believe something strange happens when converting the VISA control from 8.2 to 8.5. Its easy enough to just use strings instead of the VISA controls so that is what I did. Perhaps that is the better way of doing things anyhow.

I have identified the problem lies with using a VISA control in the class data definition. After changing it to a string in 8.2 and then saving it again in 8.5 the problem is no longer preset. I'm in contact with NI and will post more details as I get them.

Yes, this was one of the first things I tried. Unfortunately it didn't help. I also tried replacing the broken class control with the one defined in my class, but that didn't have any affect either. Luckily I did make a backup copy before moving to 8.5. So LabVIEW 8.5 will use my class in the original 8.2.1 format but after re-saving and then opening it again everything breaks. Perhaps something is wrong in the new file format which I find very discouraging.

I have taken the plunge to 8.5 and started converting a large project that I am working on. Everything was going sweet, so I figured I would add a new class. (On a side note it's much easier to add methods now with the additional templates.) And then it hit, that blahblahblah.cpp error, line xxx. Ugh! So after restarting LabVIEW and opening my project I found my classes are now broken. Since it's only affecting the ones inheriting from a specific parent class I thought it might be possible to change inheritance just to get a better idea what the damage is like. Well I can't even do that, while attempting to change inheritance LabVIEW will lock up and eat away at CPU cycles. Here is what I am seeing. Any suggestions or ideas on how to recover from such a mess would be appreciated. Thanks.

I have been using a MacBook Pro (original Core Duo) without any problems. I will sometimes reboot into windows if I think I will be spending a lot of time doing LabVIEW development, but mostly I use Parallels. One thing I have noticed is that LabVIEW requires re-activation when you change from Parallels to bootcamp, assuming you are using your bootcamp partition with Parallels. I have seen no harwdware issues using USB devices under windows from bootcamp, I have not tried Parallels. If you want to use virtualization under Mac OS and use USB DAQ devices then VMware's Fusion (still in beta) would be a better bet, it supports all USB type transactions where Parallels has had some problems.