Closed rainman110 closed 4 years ago
I had this problem, when I derived a new type from an existing cpacs type in the cpacs schema.
It turned out, that the wrong ReadCPACS was called: the generated one, not the one from the custom derived class.
This small change fixes the issue for me and does not affect any other parts in TiGL.
See this TiGL commit for more information: https://github.com/DLR-SC/tigl/commit/03e695d247e8bf5613157b986de0c8dd88ff2494
I had this problem, when I derived a new type from an existing cpacs type in the cpacs schema.
It turned out, that the wrong ReadCPACS was called: the generated one, not the one from the custom derived class.
This small change fixes the issue for me and does not affect any other parts in TiGL.
See this TiGL commit for more information: https://github.com/DLR-SC/tigl/commit/03e695d247e8bf5613157b986de0c8dd88ff2494