Include the name of the class in error messages for common error codes such as:
| 1400 |
Attempted to read flattened data of a LabVIEW class. The flat data could not be converted to the requested type because the flat data is not the same as the requested type nor is it the same as any child class of the requested type. |
| 1401 |
Attempted to read flattened data of a LabVIEW class. The version of the class currently in memory is older than the version of the data. You must find a newer version of the class to load this data. |
| 1402 |
Attempted to read flattened data of a LabVIEW class. The data was written by an old version of the class and the class in memory no longer supports loading and mutating data from that older version. |
For those of us that aren't using the AQ Character Lineator and do just simple flatten/unflatten of objects (e.g. when sending over TCP), it's pretty common to run into these errors. It would be nice to see the specific class that is showing disagreement.
---
Yes, we could probably match the *.lvclass pattern out of the flattened string, but then we have to do some wire branching just in case there might be an error...and we also can't easily wrap up that logic for generalization for anywhere that we unflatten class data (without fancy xnode polymorphism).
