04:50 <peepsalot> i object to any coaster designs with holes in them

05:48 <J1A8452> i use one - but probably they shouldn't be called coaster..  as i use it on a metal coaster to minimize adhesion due to fluids surface tension.

06:10 <peepsalot> ah, "coaster liner" maybe

06:59 <Scopeuk> Hmm I have an open scad coaster kicking around somewhere, was a lunch time print day 2 of work from home because my home coaster (HDD platter) wasn't big enough for my work mug

07:00 <Scopeuk> Looks like to 90mm one there though, solid flat with a bump on the edge, printed in tpunbecouse why not

08:14 <J1A8452> peepsalot just found "trivet"

08:16 <peepsalot> a trivet is more for hot pots of food than drinks, and larger

08:20 <Scopeuk> I suppose it wouldn't need to be larger, but yes they are generally for heat protecting a surface

08:32 <J1A8452> funny how translation works and how languages differentiate between things (or not)

08:33 <J1A8452> https://www.dict.cc/?s=untersetzer

08:45 <J1A8452> while a Bierdeckel /Bierfilz (beermat)  is  always  absorbing  and made from paper pulp - and is more or less single use

08:49 <J1A8452> originally made from wool and reused .. and not only used as coaster but also lid ..  how religion (beer monks) had influence is amazing

08:53 <Scopeuk> yes English tends to favour word for thing rather than distinguishing using further description

08:54 <J1A8452> while German is often very descriptive  ..  Bier:deckel  Beer Lid .. Unter:setzer   ⇒ set under

08:55 <Scopeuk> German also really likes compound words if I remember correctly

08:55 <Scopeuk> slightly weird to have the difference for languages that share the same root

08:56 <J1A8452> Ü yes resulting in very long words

08:57 <Scopeuk> yup

08:57 <Scopeuk> well for a given definition of words. although without how some brits speak the language you could be forgiven for thinking we take the word breaks out too

08:58 <J1A8452> Grundstücksverkehrsgenehmigungszuständigkeitsübertragungsverordnung

08:58 <Scopeuk> legally transferring ownership of a property?

09:04 <J1A8452> it is about allowance for traffic on a property and the law that says who is responsible  to transfer  this

09:04 <Scopeuk> yeh automated translation was not too helpful but legal terms tend to be a bit janky at the best of times

09:05 <J1A8452> Amtsspracheneinkürzungssoftware   --  a software to make long words shorter for official use

10:26 <J1A8452> ha https://www.printables.com/model/227853-moss-coaster

13:42 <Scopeuk> lf94 was it you I was talking to a few days ago about kinematicsa/inverse kinematics? I found my (admitadly rudimentary) reprap simpson model

13:42 <Scopeuk> https://pastebin.com/BP0UAxUb

13:43 <lf94> nope

13:43 <Scopeuk> ahh was peepsalot ^^, appologies

20:00 <InPhase> Scopeuk: Pretty neat tri-arm result. :) I tweaked up your parameter marker cubes, animation 1->0 wraparound, and dynamic sampling. Sharing back the tweaks. https://bpa.st/T54A

20:03 <pa> hmm.. kevfquinn nice way to make rounded cylinders (https://www.thingiverse.com/groups/openscad/forums/general/topic:17201) takes forever to render..

20:04 <pa> with smooth surface, ofc

20:15 <InPhase> pa: That's close to the strategy used in smooth_prim.scad's SmoothCylinder (and it's the same input parameters), except it's 7 times longer in the implementation just to handle all the little edge cases where you try to do things like make it smoother than the object itself. (e.g., try to put n=20 and keep the other parameters, and that short one falls to pieces badly.)

20:27 <gbruno> [github] Anonymous-Coward opened issue #4281 (Feature request: modules should return objects) https://github.com/openscad/openscad/issues/4281

20:29 <gbruno> [github] t-paul closed issue #4281 (Feature request: modules should return objects) https://github.com/openscad/openscad/issues/4281

21:02 <InPhase> Is the userbase growing rapidly these past few months? We're getting an uncommon distribution of issues open lately I think.

21:10 <peepsalot> i was wondering the same thing, seems odd.

21:36 <Scopeuk> InPhase neat

22:06 <joseph_> teepee InPhase: I wanted to give you an update about my progress on tracing the renderer execution. I'm having a lot of success with the strategy of placing breakpoints and tracing up the call stack to understand how the functions fit together. I haven't shared my list of questions yet because often I will end up answering one of them on my own a bit later

22:08 <joseph_> Some other schedule changes on my end have slowed progress a bit, which is why I am using the weekend to catch up. I will check in again when I think I'm at a good spot where I've reduced my set of questions to those that I'm less likely to answer on my own

22:09 <InPhase> joseph_: Ok. Structured preparation of questions is also a method to help you sort through answering some on your own (it's a trick! but one worth keeping on doing.). What you should do after answering them is keep notes of the answers and make a sort of summary of bullet point answers as notes and for a summary of comprehension progress as a work marker.

22:11 <InPhase> That will help us have some info to know if you need a redirect or tips, even if you're progressing along well independently.