Jordan Brown

To be clear: `part(...)` would turn into an AST node and then, when executed, would turn into a CSG node. (Just like `color(...)` and most other module invocations.) Yes, it...

When I last thought about this, I believe I was thinking of a two-level namespace, where the arguments to `part()` would be objects. Each parameter would provide metadata for one...

> I would like to see if I can export just one STL with multiple parts, Do you have any consumers that can read such a file?

To be clear: I don't *need* this feature, but I certainly have occasionally made the mistake of editing the library, not saving, switching to the model, F5ing, and then swearing...

[ The following is wrong; I was looking only at the gear model immediately above and not at the original problem. ] This looks like a standard convexity issue; see...

I'm sorry, my comment above was with respect to the gear model; I missed that I was coming into the middle of an issue.

I recently saw something sort of like this, where a negative object's back faces were visible, on Windows 11. But it went away.

I still like having a `$convexity` that controls the default convexity down through the call tree. If it's not set, the default could be the current 1 or some smarter...

OBTW, I cloned a copy to a new directory, and the `*.bin.scad` files seemed to survive.

Sigh. Looks like I fooled myself into thinking it fixed the problem, and need to fire up the Linux VM and check it out there.