4 ms·
Not OP, but : - you can't store objects in variables, so code looks convoluted with deep nesting as you need to apply multiple transforms to objects - there a
by ajnin 7y ago
Not OP, but :
- you can't store objects in variables, so code looks convoluted with deep nesting as you need to apply multiple transforms to objects
- there are no real variables, more like constants that take the value of the last assignment, so you can't do basic stuff like x = min(x, 5)
- you can't access object attributes (size, etc.) so it's not possible to generate features that depend on another object. You always need to have lots of parameters in scope. A simple use case would be to punch 4 holes in the corners of a box cover.
- string functions are very limited, there is only str() to convert a value to string but with no control on the formatting, there is no printf-equivalent
- heretoo 7y agoI'm able to do some of these things. Someone else said that perhaps the nightly build is different? ``` module thing(x) { cylinder(r=x,h=10); } translate([10,0,0]) thing(5); x = min(4,2) + 1; translate([-10,0,0]) thing(x); ``` works for me.
- radarsat1 7y agoYour third and fourth points are good ones. I think the first two points are mitigated by using functions and modules correctly.