Marius Kintel
Marius Kintel
I agree with @t-paul that this should be done in user-space, but ideally as a built-in user-space library, which is well-documented and maintained as part of OpenSCAD.
@carycode In terms of standard libraries: We already have MCAD. It's a loose collection or utilities, but @hyperair is trying to refactor and redesign some of that into a more...
This looks like a Qt bug: https://bugreports.qt.io/browse/QTBUG-36802 Not sure when it will arrive in Qt - perhaps 5.4.1 ?
Note: This was fixed in Qt, but still shows up in OpenSCAD. Needs further investigation
Some quick experiments using the design below, show very promising results: - Current OpenSCAD: 10m38s @ 385 MB - Without the top-level union: 1m4s @ 256 MB - Resulting STL...
Some printer software (MakerWare I think) supports multiple materials only through loading separate STL files for each material. To facilitate this workflow, we could add an option to STL export...
I agree that we should get the minimal feature set into master - it's still a bit of work to make this robust though.. We don't have any code for...
Giles ideas match mine exactly. intersection_for() is a hack made to avoid having to refactor internal workings and will be deprecatable once group() is implemented properly.
On 2013-05-08, at 16:32 , torwag wrote: > On 7 May 2013 17:49, Marius Kintel [email protected] wrote: > > > Current OpenSCAD: 10m38s @ 385 MB > > Total rendering...
I agree - collision detection would be cool. Since we only need detection, not evaluation, perhaps the clipper library could be utilized for this.