-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traceback on fixed point object #3
Comments
Hm, that is line 2698 in current HEAD. Any interesting code you've added? Anyway, defining all the properties in constructor (
Yep, LabVIEW reorders things on each save. pylabview just exports everything in the order things are stored within VI. |
I only added some code to verify that the parse function wasnt being called, nothing interesting. And some hasattr checks, since I wasn't sure what defaults to use. XML: Ok, so if I do end up using this as a way of keeping track of changes to the VI in version history, I would need to reorder the XML every time to some sort of consistent state? Or does reordering also involve changing IDs and so on? |
Yep. Most items from sections (ie. Data types) are referenced by ID. |
When running this on a realtime system VI, I get the following traceback:
I checked and the parseRSRCData function was not called for the object instance that throws the error.
Previously I received multiple warnings which may be relevant:
Also, slightly off topic, but diffing the XML file with one generated from a slightly modified VI shows a massive amount of changes. Is the order of the XML output variable, or does labview regenerate all the IDs everytime?
The text was updated successfully, but these errors were encountered: