Hi,
I played around with the switchcasedemo, inserted a globalsettings node, set the $fn to 50 and noticed some quirks.
I expected the global setting $fn being used by the cylinder, sphere and roundcube when the local $fn is omitted/empty.
That was not the case.
When the local $fn was empty with a sphere or cylinder, the local $fn was implicitly set to be 16+1*3.14116.
When the local $fn was empty with the roundcube, following code was generated for the eight hulled corner spheres:
translate([-(((1)/2)-0.1),-(((1)/2)-0.1),-(((1)/2)-0.1)]) sphere(r=0.1,$fn=);
translate([-(((1)/2)-0.1),-(((1)/2)-0.1), (((1)/2)-0.1)]) sphere(r=0.1,$fn=);
translate([-(((1)/2)-0.1), (((1)/2)-0.1),-(((1)/2)-0.1)]) sphere(r=0.1,$fn=);
translate([-(((1)/2)-0.1), (((1)/2)-0.1), (((1)/2)-0.1)]) sphere(r=0.1,$fn=);
translate([ (((1)/2)-0.1),-(((1)/2)-0.1),-(((1)/2)-0.1)]) sphere(r=0.1,$fn=);
translate([ (((1)/2)-0.1),-(((1)/2)-0.1), (((1)/2)-0.1)]) sphere(r=0.1,$fn=);
translate([ (((1)/2)-0.1), (((1)/2)-0.1),-(((1)/2)-0.1)]) sphere(r=0.1,$fn=);
translate([ (((1)/2)-0.1), (((1)/2)-0.1), (((1)/2)-0.1)]) sphere(r=0.1,$fn=);
This leads to a parser error.
I would suggest the following:
1. When the local $fn is not set (empty) in these nodes and a global $fn is set, dont generate code for a local $fn. Then the global setting is used for these objects.
2. When the local $fn is not set (empty) in these nodes and a global $fn is also not set, generate code for a implicitly set local $fn for all of these objects.
Then we have proper looking spheres, cylinders and roundcubes, not etchy ones. And we dont get parser errors.
This may also apply for other advanced rounded objects.
Kpacnaja_Shapotshka