jdegenstein

Yes, there is a lot of room to reduce the layers of function calls here and optimize the various type conversions that occur. Should I merge this and we can...

FYI I have been working on this, refactored most of the places directly using `TopExp_Explorer` to instead use `_topods_entities`. I am still looking at optimizing the overall flow of function...

@fischman Following up on your comment above, I personally do not like the proposal to automatically use `@1` as there are often times when I am creating a series of...

I would prefer to just keep it simple and let the user provide the Vector representing the starting point which is the way most current BaseLineObject-derived classes currently work. End...

Sorry for that error in `test` --> I edited the above and re-tested it in OnShape and it is still invalid. Regarding your other idea: ```py with BuildPart() as test3:...

Yes, a regular cylinder imports to OnShape just fine. Here is a screenshot of the STEP file from `test`-- and only one of the two fillets appears to be problematic...

Another data point: if I export STEP of `test` from build123d and import/export using Mayo or FreeCAD the resulting file IS valid according to OnShape. I have attached one from...

I was able to manually fix the file as indicated by the diff above, I simply changed one character from `#106 = FACE_BOUND('',#107,.F.);` to `#106 = FACE_BOUND('',#107,.T.);` and now it...

Related issue https://github.com/gumyr/build123d/issues/842 with some discussion and advice

Came across this issue, and we are seeing a struct.error unpack with a "real-world" font that causes my application to crash. Further details: https://github.com/jdegenstein/jmwright-CQ-Editor/issues/11 Had to resort to using ProcMon64...