This is some new problem we gone face in FEM. On one side we still do a lot devellopment, but on the other side people start to use FEM API. I will change it in a way it still runs and you need not to adapt it. But we need to think about this. As soon as a new FEM constraint object arises, we will brake it again. The funny thing is we are compatible with 0.17 just because there was no new object in 0.18 ... But on my repo is PR from quing feng for a new object already.HarryvL wrote: ↑Sat Mar 30, 2019 5:12 pm Something else ... I just pulled and built the latest FC source from femconcrete and it broke my fcFEM macro It looks like an additional parameter was added to the FemInputWriter constructor? I simply put another None at the initiation call of the relevant object and now it works again, but it makes me worry that any call to FC API is vulnerable? Also, it would mean that the macro would either work with 0.17/0.18 or 0.19, but not both. Any suggestions on how to manage this? Thanks, Harry
If you can not wait, just remove the latest commit before the first concrete commit. This one https://github.com/berndhahnebach/FreeC ... b12623dca0