LabVIEW crashes when modifying OOP parent class private data control or typedef contained in that control

Question

I've been seeing strange behaviour when I modify the private data control of a class, especially if it is a parent class.  It seems that those changes are not always propagated to all the VI's in the project.  This sometimes causes my project to crash with an exception error, or sometimes the problem is more subtle as it will simply write data to the wrong elements in the control (when bundling/unbundling).
I solve the problem by opening the typedef or class control by itself (i.e. not as part of the project), and then saving it.
The next time I open the project all problems are solved.  This is a difficult error to track down but I now know to keep a list of typedefs or class controls that I have modified (using subversion helps here), and then when this strange behaviour or crashes happen, I simply close the project and open each modified typedef or class outside of the project and save them individiually.
Anyone seen something like this too?

Answer 1

Hmmm.... Have not seen what you are describing -- though occasionally I will see a class that appears broken until I open it by itself outside the project.
How large is your application?
How many classes do you use?
How extensively do you use classes in the application?
Could you post a screen shot of your project and how things are arranged in it?
Does the problem seem to be related to any particular class or group of classes?
Have you tried mass-compiling your code?
Are the VIs set to separate the object code from the source?
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps