Torsten Paul

> `Features: fast-csg, fast-csg-safer, fast-csg-debug, manifold, roof, input-driver-dbus, lazy-union, vertex-object-renderers, vertex-object-renderers-indexing, textmetrics, import-function, predictible-output` There are none enabled, they would have a `*` after the name when enabled.

I wondering if it would be a better strategy having a new module with a more obvious interface so at some point later `surface()` could be deprecated.

Fixed via #5026.

@pca006132 Yes, if the branch name ends in '-macos', CircleCI will also do the macOS build. Our free plan has 500 macOS minutes per month which is only about 30...

Setting via variable has too many issues and does not scale well for multi file export. The current idea is to be able to annotate top level modules and that...

As already mentioned above, doing it via a variable is not seen as viable solution.

I tried a couple of suggestions, e.g. packaging `qt5ct`and so far nothing works. I'll leave that open, but this will have to wait for someone helping out with new ideas...

As mentioned many times before, using `$` variables will get my veto, the case @gsohler mentions is just one of those. I think the way to solve that topic is...

There is no "setting" of values on geometry, there is no program running as in for example python. The `part()` would be referenced in the AST, the syntax tree representing...

While I'm still not convinced it's the best idea to use `part()` as it will not cover any of the many other requested use cases, it should be able to...