<InPhase>
The initial design goal was full metric thread compatibility, but then I was like, "Why not just extrapolate these metric thread values for huge stuff, just in case?" Then I also ended up using it for some huge stuff. :)
<InPhase>
And I really like the resulting capability of being able to print parts that can be assembled without machined components, but still printing all the pieces without supports.
<InPhase>
teepee of course uses it for pretty colors, because of teepee's LED obsession. ;)
<teepee>
yep, and making this easiy printable instead of having to conform to some specific threading spec is very useful
<InPhase>
That'd be an excellent New Year's Eve jacket.
<teepee>
ah, yes, much better than just boring time display
<teepee>
well, except for the getting shot part due to the countdown
<teepee>
also... nozzle changing time :)
J24k13 has quit [Quit: Client closed]
J24k has joined #openscad
mmu_man has joined #openscad
mmu_man has quit [Remote host closed the connection]
mmu_man has joined #openscad
mmu_man has quit [Ping timeout: 252 seconds]
mmu_man has joined #openscad
<InPhase>
teepee: Spotted on your page, shamelessly stolen, and tweaked a bit. :) https://bpa.st/ZHQQ
<teepee>
just parameters, or also code I could update?
<InPhase>
I decided to round out the back. More style than fix.
<teepee>
cool, I'll have a look :)
mmu_man has quit [Ping timeout: 260 seconds]
<teepee>
but first checking if the 0.4mm nozzle fixed the print geometry
<InPhase>
I was going to try to fix the gaps, but I realized they were sub-nozzle and would be removed, so I clamped down my perfectionism.
mmu_man has joined #openscad
<InPhase>
I was also trying to calculate the correct spacing to remove the ledge, but after 5 minutes couldn't work out the right equation, so I just hand-tweaked.
<teepee>
:)
<teepee>
like I do also sometimes
<InPhase>
I think your circle base looked better for 2, but didn't like it as much for 3 wide.
J24k6 has joined #openscad
<teepee>
wow, that holder thingy is really out of spec with a 0.8mm nozzle and perfect with 0.4mm
<InPhase>
My current coffee packet brand appears to be narrower than yours, but also I use two at a time, so I doubled up the packets per hole.
<InPhase>
Cura for a while has required walls be 2X nozzle in width.
<teepee>
that's why I love when scad is shared, I'm seeing a number of designs where I wish they would be easily customizable
<teepee>
like the lucky-resistor stuff, he's really going to town lately with the uploads
<teepee>
I think the latest 3 or 4 design uploads are like >100 files each amounting to somewhere between .5 and 1 GB!
<InPhase>
Going to try to set this printing and make some lunch. :)
<InPhase>
I spotted your design right after receiving a new shipment of 200 coffee packets in an ugly box mangled by Amazon warehouse workers. :)
<teepee>
yeah, getting that here more and more often unfortunately
<InPhase>
So now 42 of them will be ready for pretty display!
<teepee>
a couple of years ago, packaging was really perfect, now it's mostly toss in and hope for the best, which is a very bad strategy with DHL
J24k has quit [Ping timeout: 250 seconds]
<teepee>
I may need to print a 3 column one too as I bought some additional chocolate-cappucino style sticks too
<teepee>
and those are a quite tight fit too
califax has quit [Remote host closed the connection]
califax has joined #openscad
<InPhase>
teepee: If you prefer to condition on width >=3 you are licensed to steal back my 5 or 6 lines of tweaks. :)
mmu_man has quit [Ping timeout: 276 seconds]
mmu_man has joined #openscad
<InPhase>
I was just thinking the other would be a pain to clean someday with those little internal crevices in the back.
<teepee>
pöh, it's CC-BY-SA, you can sell it if you want, and I can get your changes :P
<teepee>
right, good point. although mine is sitting in a cupboard, so it should hopefully not need cleaning very often
mmu_man has quit [Ping timeout: 260 seconds]
mmu_man has joined #openscad
mmu_man has quit [Ping timeout: 264 seconds]
mmu_man has joined #openscad
<cart_man>
teepee: Do you know how one uses ScrewHole to make a siumple Nut?
<cart_man>
InPhase: Just the man
<cart_man>
That could answer this
<teepee>
you use: ScrewHole() TheObjectWhereTheHoleShouldBePlacedIn();
<InPhase>
cart_man: Did you look at the MetricNut module call which does exactly that?
mmu_man has quit [Ping timeout: 256 seconds]
<teepee>
yeah, there should also be some examples to look at
<InPhase>
It's intended as both a usage example, and usable as-is. :)
mmu_man has joined #openscad
<cart_man>
InPhase: Ahh already made some custom size Bolt unfort :/
<cart_man>
teepee: Ok
<InPhase>
Also MetricBolt, MetricCountersunkBolt, MetricWoodScrew, and MetricWasher.
<InPhase>
The Rod modules are also useful far more often than one might think...
<InPhase>
I made those Rod modules for one purpose, and then ended up using them as base components a number of times. It's just handy. :)
<cart_man>
I just tried difference() {cylinder(20, 20,20, center=true);ScrewHole(310, 80);} but can not ever see the cylinder being deduced
<cart_man>
Ok ill check the example
<InPhase>
Yeah, it's not designed to be used that way. It's an operator on an object.
<InPhase>
I think actually that unplanned usage you did used to work in older OpenSCAD versions due to undocumented behavior of the language which was "fixed".
<InPhase>
(Although I never complained, because I believe in the merit of using documented well-reasoned language behavior...)
mmu_man has quit [Ping timeout: 260 seconds]
mmu_man has joined #openscad
<cart_man>
InPhase: so I have this config on my Bolt -> ScrewThread(35, 60, 6, tooth_angle=35); ... how can I make an appropiate Nut for that? I can not seem to be using MetricNut for it : /
L29Ah has joined #openscad
mmu_man has quit [Ping timeout: 255 seconds]
mmu_man has joined #openscad
mmu_man has quit [Ping timeout: 240 seconds]
mmu_man has joined #openscad
guso78k has quit [Ping timeout: 250 seconds]
<InPhase>
Parameter 3 is named parameter pitch, so you just have to manually specify it as pitch in the ScrewHole call.
<teepee>
quck question... any objections retiring the 32-bit windows builds?
<teepee>
I've disabled for now as the latest TBB build changes did make it fail, but there's more reasons including not even official support in Manifold
<teepee>
FWIW downloads seem to be pretty much just bots, including one claiming to collect information to prevent plagiarism in universities ;-)
epony has quit [Remote host closed the connection]
<InPhase>
teepee: Got to keep people from copying those open source binaries.
<teepee>
yep, that's way too dangerous
<InPhase>
teepee: And I'm of the opinion that the response to anyone objecting to not making 32-bit builds should be "It's 2024..."
<teepee>
imagine someone putting the openscad installer into their master thesis PDF
<InPhase>
Even Android made its final 32-bit release version 13 in 2022.
<InPhase>
And that's for phones...
<teepee>
microsoft seems to still support it :)
<InPhase>
Probably trying to relive their glory days of relevance.
epony has joined #openscad
<teepee>
well, supposedly some company was searching for Win3.11 admins lately, but maybe that was a meme, I did not look closer
<InPhase>
What has probably happened is some regulatory version locked systems, like medical equipment, require and pay for archaic support from Microsoft, and this allows them to keep funding the efforts to sustain updates to some archaic niche things.
<InPhase>
Because otherwise I doubt this would be a profitable choice.
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
SamantazFox has joined #openscad
mmu_man has joined #openscad
kintel has joined #openscad
<kintel>
teepee No objections to killing 32-bit builds. I'm clueless about the Windows ecosystem though..
<teepee>
I'll think of something to post on Mastodon, lets see if there is any reaction :)
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cart_man has quit [Quit: Konversation terminated!]
ccox_ has quit [Ping timeout: 268 seconds]
<InPhase>
kintel: I cringed seeing strcmp instead of strncmp in that PR title. That's on my "scream red flags" list. But it's okay in that context. :)
<JordanBrown1>
strcmp is generally OK. Trying to turn your strcmps into strncmps is just an opportunity for error, because the likely (incorrect) replacement for strcmp(a,b) is strncmp(a,b,strlen(a)), which is wrong both because it gets the wrong answer when b the same as a, but longer, and because if you are concerned about running off the end of a buffer you shouldn't use strlen() either.
<JordanBrown1>
You could, I suppose, use strnlen(), but requiring that you carry around the length of the buffer seems like it adds a lot of complexity.
kintel has joined #openscad
<kintel>
..or just use std::string ==
<JordanBrown1>
Yes, I was thinking that too, but my C++ is not strong enough to know what the reasons might be for using char *.