Jordan Brown

+1 on talking to the BOSL2 guys to see if they have any ideas how to fit this into their framework. My interpretation is that it would reset the transformation...

That is, it would discard the transformation matrix applied by the node's ancestors.

In a slightly deeper look, it walks the tree top-down, visiting each node before and after visiting the children. For a transform node, the "after" visit unions the children and...

You can do it in a library, and I have. The library has to implement all of the transforms, and you have it pass down the accumulated transform matrix through...

And that's one of the problems, that different implementations could do it differently.

It's a problem with trying to implement a node that resets the transformation for its children. Such a node is reasonably straightforward in a top-down scheme, but difficult in a...

I use the ability to pass $ variables to children to allow an outer module to pass information to its children. (My "wall" module can take children that create trim...

Generating multiple "parts" from one file is covered under #1608. Let's leave this one open for a request to have a way to control the "solid" value in STLs and...

A few thoughts: * Should timestamps appear (optionally) in CLI output? * Should timestamps be full date-and-time, or should they be narrower hh:mm or hh:mm:ss, or selectable? * Maybe instead...

I'm not a fan of using $ variables here either, but mostly I consider that a design detail. I think the more obvious structure is to follow the pattern established...