CSG Transforms & Operations on 2D primitives

[winksaville]

I was trying to optimize a set of transforms and operations to place text on a shape. So I thought I'd do the transforms on the text first then extrude and finally union with the shape.

It seems that doesn't work, you need to extrude and turn the 2D entity into a 3D shape first for the transforms to function as expected. After doing that I was getting the expected results.

Is it true that CSG Transforms & Operations only work on 3D shapes?

[timschmidt]

Transformations like translate, rotate, and scale as well as booleans such a difference and union should work on 2D and 3D geometry. Extrudes convert 2D geometry into 3D.

Care to share the code that didn't work?

[timschmidt]

I suppose we could also throw errors when attempting to do something 3Dish to a CSG containing only 2D geometries.

[winksaville]

I suppose we could also throw errors when attempting to do something 3Dish to a CSG containing only 2D geometries.

That would have been helpful and reduced the amount of wasted time. But it seems to me using types and/or traits would allow for zero runtime costs and allow idiots like me finding this out while writing the code and in most cases it would be flagged by all rust aware editing environments. In addition it would likely provide an even bigger reason to use rust and csgrs over other solutions, my 2 cents.

[timschmidt]

Noted. I will think on naming a bit.

[timschmidt]

I think CSG2 and CSG3 are the best names I've come up with. Still short, descriptive, and not an extra burden for typing. I'll start work on that.

[winksaville]

I like it, but may I suggest Cs2, Cs3 or Cs2d and Cs3d the G is somewhat redundant, just a thought