Closed johnsonm closed 6 months ago
As far as I can tell, this means changing Support
to AttachmentSupport
to support 0.22 dev, but that wouldn't be backward compatible with older FreeCAD versions. (At least, making that change avoids the errors with current FreeCAD dev build.) But I don't know enough about the intent of that to know whether it's a correct change.
yes, that's quite a pain.
I'm struggling to find time to maintain lattice2, so i recommend using stable freecad for now... i'll get to it eventually.
I have now discovered that stable freecad Appimage doesn't display properly on my system, but with the PR I just pushed, I at least don't see any relevant errors on the console, and the pattern is simple enough that I believe my fix is right.
I have a project using Lattice2, and in current weekly builds I get:
I previously reported this in https://github.com/FreeCAD/FreeCAD/issues/13746 and was pointed to https://github.com/FreeCAD/FreeCAD/pull/12714 where it was made clear that this breaking change was intentional to fix a real bug.
I suspect this is easy to reproduce, but merely loading CubeSet.FCStd from https://gitlab.com/mcdanlj/RSVPGameReplacementParts in the current weekly build is sufficient to demonstrate the problem.
(Because I'm a relatively new user of Lattice2 I imagine that I've made some mistakes in how I used it.)
Thanks for Lattice2! ☺