little_blossom has quit [Ping timeout: 252 seconds]
little_blossom has joined #openscad
califax has quit [Remote host closed the connection]
snakedGT has joined #openscad
snaked has quit [Ping timeout: 252 seconds]
<InPhase>
peepsalot: Oh, there was a similarly structured bottom to that pattern design? Good spot. I totally missed that.
<peepsalot>
yep
<peepsalot>
took me a minute too
<peepsalot>
InPhase, teepee the new logbot is up and in topic now :)
<peepsalot>
in case you missed it
<InPhase>
Yeah, I saw. :)
<InPhase>
And now I see the bottom.
<InPhase>
That design was one of those slow-navigating ones in the display window so I didn't look at the bottom before.
<teepee>
yep, I saw that, nice to have logs again
<teepee>
not that I anticipate more power outages, but still :)
<teepee>
for the record, it was aliens that snuffed out the whole wide city area
<teepee>
as in a metalized ballon :D
<teepee>
so we have our own area 51 now
<peepsalot>
hmm, i just noticed the email reply from whiteqquark (got sent to my spam folder), "Please note that Libera guidelines require channel topic to state that it is logged." i put the link there, but i wonder if it should more explicitly say "this channel is being logged" etc
<teepee>
love how it says "don't use near electic power lines"
<InPhase>
teepee: Do American made foil balloons get sold in Germany?
<peepsalot>
teepee: hope you're feeling well, despite particular users being difficult lately. Just wanna say I appreciate all the hard work you put in. Love you man <3
<teepee>
now if they had said don't use it near big transformers :)
<InPhase>
teepee: Well if it was released in the U.S., it wasn't released anywhere near Dresden's transformers. ;)
<teepee>
peepsalot: yeah, also InPhase is already helping a lot trying to steer the discussion
<InPhase>
Tonight I'm going to try to fix that highlighted file, and see if I can put the issue to bed.
<teepee>
I do understand his view, but I wish he would read a bit more hat people write as counter examples, so it's not just his case that might be fixed or not, there's other cases that still don't make sense
<teepee>
so just going back seems a very bad idea, for adding a special case it's at least needed to catch the correct case
<teepee>
I could live with some switch, it just will be a bit annoying to implement as I think it needs to be file based and also we can't just add a new function or something like that as that would not compile with the old version
<InPhase>
I think such a switch is mostly harmful in the end.
<teepee>
I suppose a backward compatible way similar to how cmake treats that stuff would be a top-level assignment like PRAGMA_LEGACY_SCOPING=true;
<InPhase>
I suspect this behavior was not widely utilized as a feature outside of this library.
<teepee>
well, it's unlikely in thingiverse as the libraries there are extemely limited
<teepee>
or at least we could check those
<InPhase>
Every attempt I made to look for it in searching came back to nophead's library, and his descriptions of the behavior.
<teepee>
well, not that they seem to update anyway
<InPhase>
I had actually seen his posts before talking about the file scope, but I never mentally parsed it as him implying there was a file scope processing step.
<teepee>
I guess I can think of 2 potential cases, that's this relativity library (which I never used) and that newly announced pathbuilder library
<InPhase>
I thought he just meant "in the top level of the file" when he said file scope.
<teepee>
I don't think the path builder uses $variables in an unusual way
<teepee>
right, I wonder if that really just is the performance issue
<InPhase>
teepee: Oh, and I confirmed master is still wasting time on the reprocessing.
<InPhase>
teepee: I made a code example for that. It very quickly gets horrendously bad.
<teepee>
that the file scope is re-evaluated all the time instead of processing and assigning things once
<InPhase>
teepee: At my first attempt at an example I turned a fifth of a second into like an hour by switching include to use. So I had to adjust my example down a few notches. :)
<teepee>
cool, for some reason the old ticket does not have a specific example even though Oskar seems to have nailed the place down already
<teepee>
but he never shared the exact details
<InPhase>
Yeah, remind me if I forget to post that later.
<InPhase>
It's hiding in one of my recent piles of scope examples.
<teepee>
sure, more like tomorrow for me though :P
<teepee>
must try to stop getting to bed only when the sun comes up
<InPhase>
Yeah. :) Enjoy your belated rest.
<teepee>
I do prefer that, but it's still froned upon by others
peeps[zen] has joined #openscad
peepsalot has quit [Ping timeout: 252 seconds]
ur5us_ has quit [Ping timeout: 240 seconds]
buZz has joined #openscad
buZz is now known as Guest6690
Guest6690 is now known as buZz
ur5us_ has joined #openscad
arebil has quit [Quit: My keyboard has gone to sleep. ZZZzzz…]
buZz has quit [Ping timeout: 268 seconds]
Junxter has joined #openscad
arebil has joined #openscad
ferdna has quit [Quit: Leaving]
buZz has joined #openscad
arebil has quit [Quit: My keyboard has gone to sleep. ZZZzzz…]
buZz is now known as Guest8685
Guest8685 is now known as buZz
buZz has quit [Ping timeout: 265 seconds]
buZz has joined #openscad
buZz is now known as Guest3045
Guest3045 is now known as buZz
retrosenator has quit [Read error: Connection reset by peer]
oldlaptop has quit [Remote host closed the connection]
retrosenator has joined #openscad
oldlaptop has joined #openscad
arebil has joined #openscad
<InPhase>
Well. I tried to fix the file scope issue with that library, but it was kind of a wild goose chase. The places referenced don't have any obvious failing cases to fix. I will try again with another round of asking for an example.
<InPhase>
I got pointed to a file that doesn't even have special variables in it.
<Ingvix>
hi, if I'm interested in the location of an object that's been moved with multiple translates, is there a method to obtain it other than just calculating it from all the translate instructions?
<Scopeuk>
Ingvix not at this time
<Ingvix>
is an easier way planned?
<Scopeuk>
not immimently, it is a know desirable feature howver
<Ingvix>
I see, thanks anyway
<Scopeuk>
you can perform your transforms using named vectors so they are easier to sum (so instead of translate([1,2,3]) you can do movement = [1,2,2]; translate(movement). the language will let you natively add vectors
snakedLX has joined #openscad
<Ingvix>
yeah, I'm aware. I'm just working on someone else's code and wondered if there's an easy way out
<Scopeuk>
ahh, unfortunately not
snakedGT has quit [Ping timeout: 252 seconds]
lastrodamo has joined #openscad
Teslamax has quit [Read error: Connection reset by peer]
Teslamax_ has joined #openscad
ur5us_ has joined #openscad
amahl has joined #openscad
retrosenator has quit [Ping timeout: 268 seconds]
la1yv_a has quit [Ping timeout: 240 seconds]
little_blossom has quit [Ping timeout: 265 seconds]
la1yv_a has joined #openscad
<peeps[zen]>
teepee: you mentioned something a while back about git submodules not going to work? i'm curious because that magnum library more or less recommends to do it that way
<teepee>
due to libs having documentation and stls and other stuff in the repo too
<peepsalot>
ah, user libs. ok
<teepee>
so I'd say the approach does work for someone who actively maintains that, but not for openscad distributing this as "the official library list"
<peepsalot>
any objections to integrating magnum as a cmake subproject / git submodule then?
arebil has quit [Quit: My keyboard has gone to sleep. ZZZzzz…]
<peepsalot>
it might end up being a large undertaking, but I think it will help a lot in moving our OpenGL code forward.
<peepsalot>
my only big concern is if we need to update OpenCSG code for newer GL versions, and how to handle packaging of that
<peepsalot>
it definitely needs changes if we go to a core GL profile, but maybe we can leave compatibility profile enabled and still benefit from some newer GL features
<peepsalot>
just wanted to get some input on it before I dive in deep with integrating and refactoring for magnum
<teepee>
yeah, I guess magnum is not really distributed anywhere?
<teepee>
normally I'm not a huge fan of going with git submodules, but here and due to the heavy modular magnum it might be the better option
<teepee>
maybe we can poke debian people early to get some feedback on packaging for distros too
<peepsalot>
i think there is vcpkg and homebrew, but not much in linux distros
peepsalot has quit [Killed (NickServ (GHOST command used by peeps[zen]))]
peeps[zen] is now known as peepsalot
Guest654 is now known as buZz
arebil has joined #openscad
amahl has joined #openscad
<gbruno>
[github] t-paul pushed 2 modifications 1 removals (Remove static gallery file, use generated one from separate git repo.
retrosenator has joined #openscad
<teepee>
hmm
<teepee>
gbruno: status?
<teepee>
gbruno: help?
retrosenator has quit [Ping timeout: 245 seconds]
<InPhase>
status?
<othx>
Gthx.NET version 2.08 2021-08-14: OK; Up for 1 day, 1 hour, 18 minutes, 26 seconds; mood: pretty good.
<InPhase>
Wrong one I guess.
Ingvix has left #openscad [#openscad]
<teepee>
yep, I've added github notifications to the openscad-lists repo and github claims to have the notifications delivered
<teepee>
nothing to see here though for the pull request :(
retrosenator has joined #openscad
califax has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
califax has quit [Remote host closed the connection]
califax has joined #openscad
Junxter has quit [Ping timeout: 268 seconds]
retrosenator has quit [Quit: Lost terminal]
<amahl>
by default all rendering is broken. especially linear_extrude. but spamming convexity=10 everywhere fixes all visual glitches. is there a way to fix rendering without cluttering my code? just write wrappers to all openscad builtins?
<amahl>
openscad itself should be fixed rather
<amahl>
99% of time you design an object with at least some convexity instead of none
<peepsalot>
teepee, re: magnum there's also msys2 package apparently, and ... have you heard of "hunter" package manager?
<peepsalot>
the other interesting thing about packaging is that, while there don't seem to be any official debian/ubuntu repos, the main build instructions use dpkg-buildpackage which creates a deb to install locally
<peepsalot>
https://hunter.readthedocs.io/en/latest/ cmake based package manager, seems comparable to vcpkg. but i read a little about that binaries can be stored on a server (not sure if there is are public repos or we would host our own binary servers if we went that route)
buZz has quit [Ping timeout: 268 seconds]
<teepee>
nope, I don't think I've heard of hunter
<teepee>
hosting debian packages is probably easiest on OBS as they provide the infrastructure or a full repo
buZz has joined #openscad
<InPhase>
amahl: Do you have a github account? If you like you could put up a wishlist request for a $convexity variable to be used as a default. I've thought before that this would be the better way to do this.
buZz is now known as Guest6662
<amahl>
yeah. I try to remember to do that when I get to it
<InPhase>
amahl: I feel like for a lot of designs this is a design-wide thing more than something we should be tossing into every call.
<InPhase>
The default is currently kept low for performance reasons, although I think it's not a huge performance cost to raise it a bit. Still, there are probably some designs where this causes everything to collapse into poor performance.
<InPhase>
It's a nuissance to make benchmarks though without a $convexity to even use in making them. :)
Guest6662 is now known as buZz
<InPhase>
amahl: The battery pack enclosure looks well designed... But what's it actually for? Is this for enclosed storage while out in a dirty place?
<InPhase>
Looks similar to mine. But how do you use it? The battery comes off the drill, you put it in the enclosure, and screw it closed?
<amahl>
the original batteries are charged by plugging the battery pack upside down in a charger
<amahl>
think I'll put some li-ion cells inside and add a hole in the bottom for a charger cable maybe. the pack is not supposed to be opened
<InPhase>
Oh wait, there are little holes in the top of your render. Those are for pins? So is this an enclosure for a homemade replacement battery pack?
<amahl>
yes
<InPhase>
Ok, that's what I was missing. :)
<InPhase>
Then, awesome. :)
<InPhase>
Maybe not as fire resistant as the originals, but still awesome.