00:02 <gbruno> [github] kintel edited pull request #5976 (Use Manifold for hull() and minkowksi()'s hull) https://github.com/openscad/openscad/pull/5976

00:05 <gbruno> [github] kintel edited issue #5977 (Escape out of Find puts focus in wrong place) https://github.com/openscad/openscad/issues/5977

02:05 <gbruno> [github] kintel closed issue #5977 (Escape out of Find puts focus in wrong place) https://github.com/openscad/openscad/issues/5977

02:12 <InPhase> Ooo, yay on #5976.

02:19 <kintel> InPhase Performance testing next..

02:19 <InPhase> I hope it comes back with numbers like 10x better, rather than 20% better. But let's see!

02:29 <kintel> Heh, I don't think the needle will move much, CGAL hulls are already calculated in double precision and likely pretty optimized. This is mostly about managing dependencies and reducing cross-kernel conversions

02:30 <kintel> The big win, if any, will be minkowski, but non-CGAL convex decomposition isn't solved yet

08:02 <gbruno> [github] yeager opened pull request #5978 (Adding Swedish translation) https://github.com/openscad/openscad/pull/5978

10:23 <Guest16> / 경찰차 USB 기본 외형 (직육면체)

10:23 <Guest16> / 전체 크기: 65mm(L) x 30mm(W) x 25mm(H)

10:23 <Guest16> / USB 삽입구 없음 — 향후 subtract()로 커스터마이징 가능

10:23 <Guest16> / 기본 차체

10:23 <Guest16> car_length = 65;

10:23 <Guest16> car_width = 30;

10:23 <Guest16> car_height = 25;

10:23 <Guest16> difference() {

10:23 <Guest16>     // 전체 차체

10:23 <Guest16>     cube([car_length, car_width, car_height], center = true);

10:23 <Guest16>     // 바닥을 살짝 깎아 바닥 평탄화

10:23 <Guest16>     translate([0, 0, -car_height/2])

10:23 <Guest16>         cube([car_length, car_width, 1.0], center = true);

10:23 <Guest16> }

11:42 <buZz> lol

13:16 <ashafq> Is that malware written in OpenSCAD?

13:34 <bitbasher> there are a couple of customizer issues that can be closed ..

13:34 <bitbasher> https://github.com/openscad/openscad/issues/4762

13:34 <bitbasher> and

13:35 <bitbasher> https://github.com/openscad/openscad/issues/4911

13:36 <bitbasher> the authors are complaining about things that are working the way the docs say they _should_ be working

13:44 <bitbasher> and a nother one https://github.com/openscad/openscad/issues/4518

14:40 <gbruno> [github] bitbasher opened issue #5979 (Customizer scalar value differs from that for single item vector) https://github.com/openscad/openscad/issues/5979

14:54 <gbruno> [github] bitbasher opened issue #5980 (Customizer spin-box widgets do not correctly follow specifications for their values) https://github.com/openscad/openscad/issues/5980

14:59 <pca006132> bitbasher: wiki is not docs

15:02 <pca006132> people write down existing behavior, which may be bugs or limitations, into the wiki

15:06 <bitbasher> yes .. i understand .. that is why i have been updating pages in the Wiki based on what i have seen as I explore the customizer

15:07 <bitbasher> are the docs considered to be the startment of design intent? does the customizer as currently operating match the docs and it is the wiki that is wrong?

15:54 <pca006132> do we have docs?

15:55 <pca006132> anyway, the main point is that you should think about the intent when you triage issues

16:00 <InPhase> bitbasher: The wiki docs are just documenting what is, in a manner that is a combination of devs adding things and users adding things. Intent typically lives in scattered discussions and PR notes and such. Also intent is a bit transient and wishy washy as a notion, and thus can be subject to some debate at times.

16:01 <InPhase> bitbasher: It's fundamentally a collaborative project with evolving consensus over time.

17:02 <gbruno> [github] jesseditson synchronize pull request #5972 (Add ability to build to a (wasm-based) node module) https://github.com/openscad/openscad/pull/5972

18:55 <pca006132> https://bugreports.qt.io/browse/QTBUG-137131

18:56 <pca006132> may hit someone using openscad if they use the latest qt + nvidia + new kernel I guess

18:56 <pca006132> + wayland

18:59 <kintel> pca006132 Not sure if that issue hits us, unless it triggers on plain Qt components; we don't access OpenGL via Qt for any OpenSCAD code, as we want to be able to run the cmd-line in a Qt-less environment

19:11 <gbruno> [github] jesseditson synchronize pull request #5972 (Add ability to build to a (wasm-based) node module) https://github.com/openscad/openscad/pull/5972

20:05 <gbruno> [github] kintel edited issue #1195 (Preview rendering in a separate thread) https://github.com/openscad/openscad/issues/1195

20:05 <gbruno> [github] kintel edited issue #1195 (Preview rendering in a separate thread [$100]) https://github.com/openscad/openscad/issues/1195

20:06 <gbruno> [github] kintel edited issue #1195 (Preview rendering in a separate thread) https://github.com/openscad/openscad/issues/1195

20:43 <bitbasher> inPhase : all good then! i love a wishy washy, flexible dev environment and am happy to contribute in any way wanted .. i trust that the community will take my input in the spirit i offer it in.

20:46 <teepee> ahhhhhhhhhh

20:47 <teepee> who know, there's a "ts" command :)

20:47 <bitbasher> on the matter of the bug reports i commented on - i was reviewing open bugs to be sure i was not reporting duplicate issues. i saw that 3 of the bugs i looked at were not real issues and commented to present my test results. I can see that the community might see that as triage but all i am doing is contributing some 2025 info to bugs that have sat open since 2023 .. not my place to decide the fate of a bug report

20:47 <bitbasher> ts command?

20:47 <bitbasher> what does that do please?

20:47 <teepee> it adds a timestamp infront of every line

20:48 <bitbasher> in bash or in openscad?

20:48 <teepee> bash, well, command line in general

20:48 <teepee> and I did like my: xargs -r '-d\n' -n 1 printf "$(date): %s\n"

20:49 <bitbasher> in bash and zsh i modify my prompt string to show date-time

20:49 <bitbasher> that is pretty snaky mate .. devious .. props :)

20:49 <teepee> for log output, e.g. back-up scripts

20:50 <teepee> also, from now on, the goal is to have houses look like the org sitting inside... https://mastodon.social/@nixCraft/114692994030113356

20:51 <teepee> anyway, I saw your comments and I suppose one of the bug reports might be converted to a feature request

20:51 <bitbasher> hey .. speaking of logs .. the console log in OS .. is that copied to a file anywhere? i keep having to right click save to be able to scroll back through echo'd feedback

20:51 <teepee> no, it's not saved currently

20:52 <bitbasher> idd .. i love the fish

20:52 <bitbasher> which bug would u promote .. all three looked like dead issues to me

20:53 <teepee> there's no such thing as a dead issue

20:53 <bitbasher> or .. do you refer to the new reports i put in today?

20:53 <teepee> I think it was the string display for customizer

20:55 <bitbasher> oh .. well .. i certainly have a diff approach to old bugs .. i dont like deadwood in my debt pile so i close things and let time bring more evidence of a real problem

20:55 <teepee> well, if it's closed, yeah, but open and old is different

20:56 <teepee> if it's valid, it does not get less valid with time if nobody has time to work on it

20:56 <bitbasher> the suggestion i liked was the colour selector .. no idea how to offer a pop-up selector pallette from the customizer .. i have no clue

20:57 <teepee> I think for all the extension stuff, we would want to have our own native customizer syntax

20:57 <teepee> not it's not *strictly* needed but extending that thingiverse comment stuff seems not a good idea

20:58 <bitbasher> anyway .. at least two of the bugs i commented on are actually misunderstandings about the way the customizer works so .. nothing to fix

20:59 <teepee> yeah, I think the include one is both intentional and ok to keep

20:59 <bitbasher> are openscad scripts actually usable on Thingiverse?

21:00 <teepee> hit and miss

21:00 <teepee> plus even more ancient version than the last release

21:00 <teepee> and only single file

21:00 <bitbasher> but my testing of include files showed the wiki to be correct .. customizer will not look for params in an included files

21:00 <teepee> unless they did work on the customizer lately... I'm not really using thingiverse for years

21:01 <teepee> yep, that behavior is intended

21:02 <teepee> actually there's extra code needed to exclude those parameters as otherwise include<> behaves like low level copy&paste

21:02 <bitbasher> humm .. so in fact the bugs i put in today (on customizer issues) can possibly be discarded in in favour of making a new sort of customiser that suits OS better?

21:03 <bitbasher> i mean .. if we chose to abandon the thingiverse style param thing

21:05 <teepee> we can keep it for stuff that uses it

21:05 <bitbasher> i really like the customizer actually ..

21:05 <teepee> but it would be nice to have a builtin version that allows a bit more options

21:06 <teepee> the gui could work for both ways of specifying things

21:06 <teepee> but the native one could have extra things like color selector, font selector, ...

21:07 <bitbasher> following the example of a gear making script i saw on thingiverse .. it has a selector that lets one exercise every function in a library and still allow it to be used as an included library in other scripts

21:08 <bitbasher> i am still working on it but i will publish .. soon :)

21:19 <bitbasher> night night all

21:20 <teepee> good night