04:21 <J25k78> biscornu  - made something .. but i don't use signal

05:53 <gbruno> [github] Riesi opened issue #5998 (WRL export looks broken in Kicad (nightly/git)) https://github.com/openscad/openscad/issues/5998

06:13 <J25k78> @biscornu so if you reading this, I made a simple print in place version ..

08:59 <bitbasher> can someone point me to where function / module pop0up syntax info is in the app .. when i hover over linear_extrude in the edit window the syntax info is way out of whack to the wiki page .. i would like to see what is really there in the code, the pop-up into and make the docs match

10:16 <J25k78> !cheatsheet

10:16 <J25k78> cheatsheet!

10:16 <othx> cheatsheet is https://www.openscad.org/cheatsheet/ for the release version and https://www.openscad.org/cheatsheet/snapshot.html for the development snapshot versions

10:23 <bitbasher> can there be links between the two cheatsheets please? and .. i found the release cheatsheet in the docs folder .. are you doing something manually to place the snapshot version in the folder?

10:23 <J25k78> ah shit someone renamed the headline again

10:23 <J25k78>  {"height", "v", "scale", "center", "twist", "slices", "segments","convexity", "h"}

10:25 <J25k78> afaik some script is doing some sync.

10:27 <bitbasher> ah .. u guys are are answering my question about linear extrude .. thanks .. but i would like to look at the text that is popped up in the edit panel when you hover over a call to linear_extrude .. basically where is the command line completion stuff

10:34 <J25k78> here are the cheetsheets https://github.com/openscad/openscad.github.com/tree/main/cheatsheet

10:34 <bitbasher> thanks .. and the texts used in command line completion?

10:52 <J25k78> bitbasher can you say what the problem is? or open a ticket

13:13 <buZz> so eh, i need 'some airflow duct' for a fan nobody used for 'aux partcooling' yet

13:13 <buZz> fancy CADs have airflow stuff to model optimal shapes for that

13:13 <buZz> is there some fossy method for similar?

13:17 <buZz> i just found https://www.openfoam.com/

14:36 <DedoVerde> Hey again, just wanted to give an update on the issues I ran into with the 2021/2025 rendering or preview speeds: it all somewhat solved itself, in that, as soon as I started using an external lib I needed for some stuff the preview speed in 2021 became much slower than in 2025, so I'm only using 2025 now - thus, issue solved, sort of, yay! I had tried to create a file to reproduce the

14:36 <DedoVerde> problem but gave up after a few hours... maybe I can share the whole model after all though, once I changed it up more, it's still all heavily WIP. Thanks anyway for the help and the awesome tool :D

14:40 <bitbasher> sure .. there is no problem exactly .. i was experimenting with linear_extrude the other day .. when typing the modules name into the editor window it does the command line completin thing

14:40 <bitbasher> it showed parameters that did not match the docs in the popup .. and did not mention the v for vector parameter at all

14:41 <bitbasher> so i was thinking to look at the code and cmd line completion stuff to see how to rationalise it all

14:52 <InPhase> DedoVerde: If you are using Manifold, 2025 is, on purpose, much faster than 2021 at rendering.

15:00 <DedoVerde> Yeah, I got that much ;) The fun part was that for me, 2021 was actually 10-20x faster than 2025 with Manifold, in this specific scenario, when previewing a scad file that was just saved from another instance... it was a bit complicated and weird but I spoke with kintel about it; he requested a file to reproduce the issue and I'll try to get one I can share

15:14 <DedoVerde> So yeah, thanks again and I'll be back hopefully with a test model soon :D

15:56 <pkriens> Is there any documentation concerning the use of smart pointers? I am trying to extend Let::evaluate to support that 'let' can become a value object but I don't seem to be able to get the memory management right. When I use simple values it is ok but when I use a function it crashes. The changed code is here:

15:56 <pkriens> https://github.com/openscad/openscad/compare/master...pkriens:openscad:master

15:56 <pkriens> Any pointers appreciated.

19:43 <kintel> bitbasher: The tooltips are built from the actual OpenSCAD internal API definition. If you start by reading this, you might find your way to the individual API definitions (they're defined together with their implementation): https://github.com/openscad/openscad/blob/master/src/gui/ScadApi.h

19:50 <kintel> pkriens: Re. "let can become a value object": Are you essentially trying to create a JSON-like object so that e.g. myobj = let(a=1, b=2, c=3); becomes equivalent to myobj = import("myobj.json"), where json is {"a": 1, "b": 1, "c": 3} ?

19:51 <kintel> This sounds a bit like JordanBrown's territory :)

19:51 <InPhase> For which there was a PR.

19:52 <kintel> yeah, so I would suggest touching base with him, and/or read that PR or the corresponding PEP, or read the code for the import-function feature before digging too deep into yet another implementation

19:54 <kintel> Use of smart pointers was retrofitted into OpenSCAD, and I thing there are still naked pointers floating around in various places, plus shared vs. unique pointers are often not used in a consistent fashion, partially to be able to update/improve code locally without touching every single file.

19:55 <kintel> I tend to do significant refactoring prior to landing features when I discover things that make my life hard, but that's often out of reach for casual contributors.

20:05 <Guest0> hey there

20:10 <J25k78> hi