<kintel>
guso78 Yes, to instantiate modules, you need a lexical context and a dynamic context, so that's the purpose of the two ("defining_context" == lexical context)
germ has joined #openscad
kintel has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<InPhase>
teepee: Done and posted, as tutorial 7. I think it follows nicely from yours, but probably does not clobber anything you were thinking of also talking about.
<InPhase>
teepee: I was originally thinking of trying to present Bezier recursion or something as a demo, but I think what I came up with instead is more instructive, and also, Christmasy.
<teepee>
guso78k: we should not have that with the normal builds, that's a Qt path issue and should be taken care of by either AppImage or not happen with the full containerized installations like Snap and Flatpak
<guso78k>
teepee, I believe this issue only happes with the tar.gz tarball release. Analysing the release script, I understand that the script copies all the shared object dependencies and relocates to the copy. So it also does for the qxcb object. that means, that there might be an old qxcb shared object in the release package, whereas the user's graphics
<guso78k>
card only works with the system installed one ?
<teepee>
that's what I said, there's no official tar.gz release anymore, due to all those issues
<guso78k>
understood. Still it would be great to have/work on infallible tar.gz releases because they are really tiny compared to AppImages. Lets see if i can spare time on that in the future.
mtm has quit [Ping timeout: 252 seconds]
mtm has joined #openscad
guso78k has quit [Quit: Client closed]
germ has quit [Ping timeout: 264 seconds]
snaked has quit [Remote host closed the connection]
<InPhase>
teepee: Although I noticed the gifs seem to have longer delays between frames that felt right to me. Perhaps that sentiment arose though since I had 8 steps. Although they're basically 8 micro-steps.
<InPhase>
I tried to break it down very gradually.
<teepee>
that's perfect, it's a tutorial after all :-)
<teepee>
picking things up with extrusion for part 8
<InPhase>
I was actually going to do the holder too, but then I saw I was at 8, and assigned it as homework, following the previous thinking on that. ;)
<InPhase>
Yep. I did no linear_extrude, but only did rotate_extrude.
<teepee>
maybe the holder can be created differently for another part?
<InPhase>
Possibly, yeah. I want to do something a little more involved with math inside of functions. I just didn't figure out what yet. The candle was sort of stream of consciousness generated on the spot.
<teepee>
feel free to grab some slots of next weeks advanced section
<InPhase>
I'll probably want to do something with module nesting or recursion too, since that can be a lot of fun.
<InPhase>
I was thinking about that 2019 Christmas Tree I did. Maybe something along those lines, but perhaps a little different, and in a stepwise manner.
<InPhase>
Not sure yet.
<teepee>
I guess the plan for this week is ok, next week is still 100% open, just random suggestions in the document ^
J24k48 has quit [Quit: Client closed]
J24k48 has joined #openscad
<J24k48>
isn't rotate_extrude first in part8
mmu_man has quit [Ping timeout: 252 seconds]
mmu_man has joined #openscad
<teepee>
J24k48 InPhase used it in part 7 for the math shapes
<teepee>
it's cool, not much explained in that part, but getting a closer look in the next
<J24k48>
yes that is why we may should switch 7 and 8
<teepee>
nah, a bit of teasing should be good
<J24k48>
so today using .. tomorrow learning how - Ü
<teepee>
yes, using it but focus is on the math
<teepee>
I agree that we should not do that a lot, but a) it's also an advent calendar and b) too strict might be also boring
<teepee>
part 6 also cheats a bit by using text() without much introduction ;-)
mmu_man has quit [Ping timeout: 265 seconds]
teepee_ has joined #openscad
mmu_man has joined #openscad
teepee has quit [Ping timeout: 264 seconds]
teepee_ is now known as teepee
pca006132 has quit [Read error: Connection reset by peer]