Cubes with tube and text

[winksaville]

I've created a small cube, 2.4 mm on a side, with a tube in the center and printed text on the side with the diameter in microns. Can be improved but I thought someone might be interested.

[timschmidt]

First: Awesome work!

A minor nit: on line 16 you write:

let csg_text: CSG<f64> = CSG::text(&text, font_data, 4.5, None);

Where you probably want:

let csg_text: CSG<()> = CSG::text(&text, font_data, 4.5, None);

As whether csgrs uses f32 or f64 is selected by cargo features at compile time, and the type in <> is the metadata type. Which you're probably not using, so (). This may be reworked in the next couple releases.

I have some positioning functions in the queue to make modeling like this easier. I want to work them in as part of the attachments system.

[winksaville]

I haven't done this before, in your example dependency you set default-features=false so I have to mention all the defaults and then either f32 or f64?

[timschmidt]

Right. f64 is on by default. And Cargo doesn't offer a way to turn off just one default feature that I know of, so you have to turn them all off, then re-enable the ones you want.

[winksaville]

Hmm, this works:

[dependencies.csgrs]
version = "0.16.0"
default-features = false
features = ["f64", "stl-io", "dxf-io", "truetype-text", "hershey-text", "chull-io", "image-io", "metaballs", "hashmap", "sdf", "offset"]

But changing "f64" to "f32" fails to compile, is there something else I need to do or maybe it hasn't been tested recently :)

[winksaville]

This isn't critical now, f64 is just fine.

[timschmidt]

Looks like geo assumes f64 in a few places that cavalier_contours was more fully generic over. I will have to get it back in shape.

[winksaville]

NP, work on thing more important, do you want me to create an issue?

…

On Mon, Mar 17, 2025, 19:00 Timothy Schmidt ***@***.***> wrote: Looks like geo assumes f64 in a few places that cavalier_contours was more fully generic over. I will have to get it back in shape. — Reply to this email directly, view it on GitHub <#32 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH2CHHJMP3D4IXQEQ6OHNT2U544RAVCNFSM6AAAAABZGPDFXGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENJTGIZDEMA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[timschmidt]

Sure, thank you.

[winksaville]

Done, #33