[OpenSCAD] Preserve "holes" in module objects

Jerry Davis jdawgaz at gmail.com
Fri May 1 23:27:36 EDT 2015

you know, I have wondered this too.
I come from a OO programming background.

I kinda consider a module as an object (sort of). And it would be nice if
whatever the module "produced" remained intact.
So, If I made a union() with that module, it would add whatever the module
produced to the final result.
Same with difference(), whatever the module "produced" would be
differenced() (if it was second ... n in line of course)

Is that what you are looking for?


Extra Ham Operator: K7AZJ
Registered Linux User: 275424
Raspberry Pi and Arduino developer

*The most exciting phrase to hear in science - the one that heralds new
discoveries - is not "Eureka!" but "That's funny...".*- Isaac. Asimov

*f you give someone a program, you will frustrate them for a day; if you
teach them how to program, you will frustrate them for a lifetime. *-

*If writing good code requires very little comments, then writing really
excellent code requires no comments at all!*- Ken Thompson

On Fri, May 1, 2015 at 8:21 PM, Marius Kintel <marius at kintel.net> wrote:

> On May 1, 2015, at 21:29 PM, jellsworth <jerry.ellsworth at gmail.com> wrote:
> > *Is there a way to preserve critical "empty space" in an object created
> by a
> > module, even when embedded in another object?*
> >
> Interesting question.
> The typical way of solving this is to perform unions first, then
> differences. This would require you to split up your modular objects in two
> though.
> What you’re after sounds a bit like a “mask”. Not sure how we would
> implement that though, but ideas are welcome.
>  -Marius
> _______________________________________________
> OpenSCAD mailing list
> Discuss at lists.openscad.org
> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscad.org/pipermail/discuss_lists.openscad.org/attachments/20150501/dfa5d25b/attachment-0002.html>

More information about the Discuss mailing list