10-15-2010 03:48 AM - edited 10-15-2010 03:50 AM
Hello NI,
I have to report a bug which causes LV 2010 to crash with error in "datamgr.cpp", line 2720. This crash is reproduceable.I use LabVIEw 2010, 32 bit on Windows 7.
To cause this crash you have to perform the following steps (I attached a sample VI to reproduce these steps.):
The problem is to change the representation of the cluster element, where the cluster is part of a typedef. A solution is to forbid to call the “Customize”- editor directly from the FP (not nice) or to forbid to replace the orginal control, instead force the user to save the altered control to a .ctl (nicer).
This shows a general problem with TypeDefs, where the array of a not-typedefed cluster is typedefed. This was discussed earlier with the cursor list of waveform graphs (couldn’t find it anymore, but read it in this forum) where this problem also can occur. So this is an appeal to National Instruments to change the TypeDef to the clusters and make arrays of them.
And, after all, for me it is unexpected behaviour that a constant / control / indicator, created from a property (or any terminal / node I can find on the BD) has another datatype than the original terminal or node.
Greets, Dave
Picture 1: Type of property node
Picture 2: Type of created control
Picture 3: Error message
10-18-2010 09:17 AM
This is a BUG,
where can I anounce this?
greets, Dave
10-22-2010 10:55 AM
Dave,
This is a good place to report a bug. One of our applications engineers will investigate and file the appropriate request with R&D to get it fixed.
Regards,
Simon
10-25-2010 01:15 AM
Hello Simon,
thank you.
greets, Dave
11-01-2010 03:59 PM - edited 11-01-2010 04:00 PM
This was reported to R&D (CAR # 252799) for further investigation.
11-18-2010 12:15 PM
Hi All,
I am also facing the same bug from the long time which causes loss of data unexpected.Please solve this bug and tell me any way to solve this.I am using Control Type Def in my project.
Thanks
Yogeshwar
11-22-2010 05:06 PM
Just to give you folks an update, CAR # 252799 turned out not to be the same issue you are experiencing here. This bug has been reported as CAR # 275825 instead.
01-12-2011 10:59 AM
Was this issue ever resolved...?