00:18 <kintel> Looks like the culprit is the trick for allowing undocked windows to float behind the main window: https://github.com/openscad/openscad/pull/2930

02:02 <kintel> Is it actually working to float undocket widgets between the main window? Testing on macOS indicated that it doesn't actually work, but perhaps it works differently per platform?

02:18 <teepee> on Wayland it's pretty broken as the windows don't get decorations

03:39 <kintel> The docking stuff is pretty annoying in general, but we don't really have a better/easy mechanism to deal with tool windows: (

03:54 <gbruno> [github] kintel pushed 5 modifications (Cleanup application exit code (#5668)) https://github.com/openscad/openscad/commit/615787a1ae65f339f0eb697604caf204e4e17c4c

03:54 <gbruno> [github] kintel closed pull request #5668 (Cleanup application exit code) https://github.com/openscad/openscad/pull/5668

06:23 <joso> Hi all. Today discovered the measuring tool, but I cannot for the life of me get it to work :(

06:24 <joso> I've read that I need to be using a rendered model, and in manifold mode

06:24 <joso> I have a rendered model, but I'm having issues with using manifold mode

06:24 <joso> At least, I read that you can find it in Preferences -> Features -> Manifold, but it isn't there

06:25 <joso> I went to Preferences -> Advanced -> 3D Rendering, and selected manifold there, but with that the measuring tool is still not working

06:26 <joso> I'm using the latest weekly image (2025.02.16), but also had the same behavior with 2025.02.01

09:07 <guso78> Joso IT only works after F6 render

09:08 <guso78> Manifold has to be Set in Backend Option

10:50 <church_> joso: not sure it's that useful, not always one can mark exactly wished place/edge .. and i hate that after use it cannot be "disabled", with selected model elements distance or angle measured staying highlighted forever. Meanwhile manifold render by itself, by it's 10-100x perf increase, is more then worth it

11:03 <church_> hmm, somehow google didn't return me useful examples of "manual" by segments rotate extrude analog, can someone point me to such, to adapt? :) (hit need to hull together few rotate extrudes, concavity/relative spacement/and "all points must be on single axis" prevents 2-d hull & rotate-extrude it)

16:00 <kintel> We should probably clean up the measuring tool before the next release. How to use it is a recurring question on the mailing list as well. I feel it's mostly about tuning the UI + some way of discovering why it doesn't work in certain situations

16:47 <gbruno> [github] kintel closed issue #1768 (Provide simple measure tool [$65]) https://github.com/openscad/openscad/issues/1768

16:57 <gbruno> [github] kintel opened issue #5672 (Make interactive measurement tool release ready) https://github.com/openscad/openscad/issues/5672

18:41 <church_> kintel: my suggestions: 1) have measuring tool buttons not in toolbar or greyed out, if for some reason they cannot be used, 2) have them as radio button, that can be left switched on and CAN be switched off w/o reloading app/model anew. Like eg. show axis buttons and alike, to not annoy for staying on after use ... P.S. as for req. of manifold + F6 render .. there might be also short popup to remind to switch manifold in options on and render at least

18:41 <church_> once, if not yet

18:41 <church_> or not popup, maybe text echoed in log

18:42 <kintel> Yeah, sounds reasonable.

18:54 <teepee> taking out buttons after f5 and adding after f6?

19:09 <kintel> perhaps greyed out, with a tooltip or smth. explaining why?

19:16 <teepee> yes, that seems much better

19:16 <gbruno> [github] kintel closed pull request #5666 (Remove Ubuntu-20.04 builds, as GitHub will turn down the runner on 2025-04-01) https://github.com/openscad/openscad/pull/5666

19:16 <gbruno> [github] kintel pushed 1 modifications (Remove Ubuntu-20.04 builds, as GitHub will turn down the runner on 2025-04-01 (#5666)) https://github.com/openscad/openscad/commit/3d6fec95047ee10de581f8d322d9eba8d3c09f67

19:19 <kintel> Anyway, I added it as a potential blocker for next release. Good to get it sorted, just tedious to write GUI code : /

19:20 <kintel> Btw., related to my hang issues yesterday, turns out that my exit fixes combined with https://github.com/openscad/openscad/pull/5630 fixed everything :)

19:33 <teepee> nice!

19:35 <gbruno> [github] t-paul edited issue #5425 (problem with path after openscad-2024.10.28-x86-64) https://github.com/openscad/openscad/issues/5425

19:42 <Guest57> church_ you can disable the selected edge by pressing "Escape" . this is the most logical key to exit a command

21:29 <church_> Guest57: LOL. Most logical, maybe .. but i didn't think of that, when used "mouse UI" :). Also inconsistent with those other widgets, that can be switched on/off and also show state that they are "on" (show axes/scale markers/edges)

23:07 <TylerTork> Looking for a best practice for notifying a user that their inputs in the customizer are incompatible with reality. Ideally it would be something noticeable in the preview panel. Echo doesn't really cut it as this message is too easy to miss. I know assert is more noticeable and shows a banner in the preview window, but it also displays a stack

23:07 <TylerTork> trace which is unnecessary in this context. I thought to use the $vp variables to create some in your face text, with code shown below, but I don't seem to have a way to control for the size of the panel, so sometimes it's not an optimal size:

23:07 <TylerTork> include <BOSL2/std.scad>

23:07 <TylerTork> module notice(text) {

23:07 <TylerTork>  lines = is_list(text) ? text : str_split(text, chr(10));

23:07 <TylerTork>  wMax = max([for (li=lines) textmetrics(li, 1).size[0]]);

23:07 <TylerTork>  echo(wMax);

23:07 <TylerTork>  sz = $vpd * $vpf / (38*wMax);

23:07 <TylerTork>  offs = sz*len(lines)/2;

23:07 <TylerTork>  translate($vpt)

23:07 <TylerTork>  rotate($vpr)

23:07 <TylerTork>  for(i = [0:len(lines)-1])

23:07 <TylerTork>   back(offs - i*sz) text(lines[i], size=sz*.80, halign="center", valign="center");

23:07 <TylerTork> }

23:07 <TylerTork> notice("Alas, container\nhas been specified too small\nfor what it contains.");

23:08 <TylerTork> https://prnt.sc/vO-6CbsDE4v1

23:08 <TylerTork> Suggestions?

23:17 <teepee> suggestion, no, but I suppose some sort of warning style info might be doable

23:21 <TylerTork> teepee: you mean as an added function in the client to display a message in the preview window similar to this?

23:22 <teepee> probably not in preview, more likely similar to the popup above the viewport

23:24 <teepee> difficult to add even more variations of info

23:24 <TylerTork> I suppose that would do. I've been improving the notice function though and I think I would still like that better -- if only I could adjust to the window size.

23:26 <TylerTork> I don't suppose there's a way to script adjusting the preview to "view all" like the toolbar button does?

23:28 <teepee> not sure, if you know the bounding box, it might be possible to do the same calculation

23:28 <teepee> easy way: no

23:31 <TylerTork> Shouldn't ONE of these numbers change when the window size changes? What use it the $vpf if it doesn't reflect what's actually visible?

23:35 <TylerTork> Like it currently says FOV is 22.5 degrees... if I make the pane half the size, it doesn't resize the contents, just lets me see less of them. Am I not now at 11.25 degrees? Why doesn't FOV change?