Doug Moen

I agree that AppImage is the best choice for some users. I personally prefer AppImage for some of the software I use. Also, there can be more than one distribution...

@A-G-D Thanks! Please submit a PR.

Thanks to @A-G-D we now have a Curv AppImage build in github actions. Due to the nature of AppImage, this will only run on "sufficiently recent" versions of "major" distros....

Whoops, sorry @ivocavalcante, I should not have posted something inflammatory to the discussion. I edited the comment to make it more factual. And yes, it's true that I have allowed...

There are workarounds. You can slightly overlap the two cubes, a workaround I am familiar with from OpenSCAD. Lee reports that you can use `smooth 0.001 .union` instead of `union`....

I have added a new mesh generator based on libfive Dual Contouring. The two mesh generators are: * `-Omgen=#smooth` -- the original and still default mesh generator based on OpenVDB...

I'm not sure about multi-key combinations, or repeated presses of the same key to toggle through states. That sounds a little complicated. However, I would endorse a simple interface that...

You want to separate a shape into 'multiple bodies', and you assume that each 'body' corresponds to a single mesh. This isn't quite true. I will define a **Mesh** as...

> Maybe curv needs a concept of material ID or part ID to correctly separate the bulks in this case. I have several ideas on how to implement this. 1....

This strikes me as a very "researchy" project, requiring iteration over multiple designs. > In Compiled_Shape, part would be a discrete function. e.g. input [x, y, z] and returns ["widget",...