Torsten Paul

The use in code is not yet centralized, so right now there are multiple places that need to be updated to use the configurable name: https://github.com/openscad/openscad/blob/811ef8cd64ea5ca4e064a7ecb8a65e10f1baf0fd/src/python/pymod.cc#L95 https://github.com/openscad/openscad/blob/811ef8cd64ea5ca4e064a7ecb8a65e10f1baf0fd/src/python/pymod.cc#L119 https://github.com/openscad/openscad/blob/811ef8cd64ea5ca4e064a7ecb8a65e10f1baf0fd/src/openscad.cc#L815 https://github.com/openscad/openscad/blob/811ef8cd64ea5ca4e064a7ecb8a65e10f1baf0fd/src/python/pyopenscad.cc#L324

The only case where this would make sense would be cases where the model that is split is imported as a single object. I'm not sure that's something OpenSCAD should...

If the separate parts are *already known* to OpenSCAD there is no need to have a slicer style "split mesh" operation when doing an export.

No, it's not need. Example with https://github.com/hugokernel/OpenSCAD_Dovetail ``` ... // Now, cut ! // Extract the first part... intersection() { amazing_design(); cutter(position=[0, 0, 0], dimension=dimension, teeths=teeth, male=true); } // ......

Hence "(**Mis-**)using".

> Your dovetail solution is interesting but if I were to ask you to add clearance between the dovetails then it becomes a little more involved. Far easier to subtract...

> Nor am I interested in making OpenScad aware of the separate parts. The model may be worked on is separate pieces in separate scripts. Ok. That is exactly why...

@jimb15122 sorry, no. That is very much out of scope here. It's specifically about the case *without* declaration in the script itself.

If you don't give any context, there's nothing to talk about (which OS, what type of OpenSCAD installation, what OpenSCAD version...). I don't see any delay here (Debian/Testing, normal package...

Check you have "Enable remote print services" disabled (should be disabled by default).