(2025-04-03, 5:56)Peter Blomberg Wrote: Perhaps the order of events is the key? To mitigate this type of thin gaps, one should first round to desired number of decimals and only then run Rectifier.
That's the ideal way - not reality. In real life, people might round and then rectify, but then there are things to fix/optimize/redone. The once ideal rect gets re-used/scaled/repositioned/re-rounded and suddenly the gaps start showing up ... for what: to save one line of code in a rect1.dat. The library is a constant work in progress, and I wonder how many of us inline rects before they start fixing things? Actually hands-up, who uses rects by manually position/rotate/scale them in an editor? We have rects 'cos we have Rectifier. Does it save you time and effort? Do you benefit from the existence of this series of prims?
I stopped generating them a long time ago 'cos the trouble they cause is by far greater than their benefit, and I wish I could turn off that "Convert bordered rhombuses into rects primitives" in LDPE by default.
w.
LEGO ergo sum