00:01 <church_> TylerTork: you want hard to miss visual cue to warn user? - do some logical check in model code, that will change color of some part of whole model. or will display it with # (transparent red, usually used to prefix code you want to set appart from rest)

00:02 <church_> eg. if(howeveryoufindouterrorstate) { #part(); } else { part(); }

00:03 <church_> or change with color("somecolorname"). or add text in model somewhere on top.

00:04 <TylerTork> Here's another question: What's the best way currently to automatically wrap a long message to a given line length, breaking at space characters and other sensible places?

00:04 <church_> though FOV .. that sounds of generic viewing in openscad, not model specific. so it's not about model, but in general about openscad UI?

00:07 <TylerTork> church_ The code I posted above is using the $vp parameters to try to create text sized, rotated, and position so as to fill a reasonable portion of the preview window. The problem is none of those numbers seem to account for the size of the preview area as a proportion of the overall window size -- because resizing that pane doesn't also zoom the

00:07 <TylerTork> pane.

00:07 <church_> i just accepted as given that openscad's text rendering is too limited. at most i'd do text splitting into rows and alike externally. best i see regarding textmetric() function that you can pass same string/same font parameters as for text(), and query eg. result size/width/length/height/spacing and so on ..

00:08 <church_> so i use text() only for relatively small text, like small line/writing, not anything that would need splitting, not anything of multilines

00:41 <kintel> TylerTork FOV isn't calculated based on user-resized windows; it's set to determine how user-resized windows should adjust camera settings

00:41 <kintel> ..and I believe it's vertical FOV, but I could be wrong. ..meaning "half viewportsize" should behave differently depending on in which direction you halve it

01:03 <TylerTork> kintel: okay -- but the fact remains that they do not adjust.

01:04 <TylerTork> ok it rescales if you change the height but not if you change the width. Odd.

01:08 <kintel> TylerTork That's what vertical FOV means. $vpf is something you write to. Resizing the window is not going to change it

01:09 <kintel> ..or are you saying that writing to $vpf doesn't work?

01:32 <kintel> FYI: I've added a new repo to the OpenSCAD org: https://github.com/openscad/tree-sitter-openscad

01:33 <kintel> This is a parser typically used as the basis for writing OpenSCAD LSP language servers. It's maintained by https://github.com/mkatychev

01:53 <gbruno> [github] kintel pushed 2 modifications (Allocate modal dialogs on the stack to simplify memory management) https://github.com/openscad/openscad/commit/04836b617470fdb57c20b72ce4f7a7a94baeb45c

01:53 <gbruno> [github] kintel synchronize pull request #5646 (Use new FBO wrapper in MouseSelector) https://github.com/openscad/openscad/pull/5646

01:55 <church_> kintel: stupid question (as in 95% cases answer to such in relation to anything is usually "when it's ready") :) - but any aproximate guesstimation of when next stable release is planned? half a year, year, two years, more? :)

01:56 <mkatychev> Oh, you mean for tree-sitter-openscad?

01:57 <mkatychev> whoops

02:02 <kintel> church_ Since we're all doing this on our spare time, it's very hard to say, depends on how lives of people involved are progressing.

02:02 <kintel> I'd say, a single person with 2h per day effective contribution could probably pull it off in a year

02:03 <church_> kintel: just that imho manifold is too tasty of addition that even those that for whatever whimsical reasons stick to 'stable', would deserve to get sooner :)

02:04 <church_> or if some stick to 'stable' as lowest common denominator for intercompatibility, also might by large be swayed if new 'stable' version pops up

02:05 <kintel> I agree, but backporting manifold to stable isn't going to happen, so we'll have to see it through. ..but we can cut some corners, like not promoting any more experimental features to stable, and if needed remove some feature we cannot make stable. No real plans though, it all come down to what we experience on a weekly basis

05:05 <gbruno> [github] kintel pushed 8 modifications (Calculate edge color from current face color) https://github.com/openscad/openscad/commit/cf2596718c99e4b7239de1256ed36f73e750d5ff

05:05 <gbruno> [github] kintel synchronize pull request #5530 (Introduce PolySetRenderer and add support for wireframe overlay) https://github.com/openscad/openscad/pull/5530

05:29 <TylerTork> I've been searching the Internet and github, and it looks like at present there is no support for exporting color information from OpenSCAD client. Is that correct?

05:30 <kintel> You can export 3MF or OFF with colors, provided you use the Manifold backend

05:32 <kintel> Pending release notes aren't merged yet: https://github.com/openscad/openscad/pull/5514/files

13:22 <gbruno> [github] Nexusnui opened issue #5673 (Add LDraw Colour Codes to Named Colors) https://github.com/openscad/openscad/issues/5673

13:34 <gbruno> [github] Nexusnui edited issue #5673 (Add LDraw Colour Codes to Named Colors) https://github.com/openscad/openscad/issues/5673

17:45 <gbruno> [github] kintel synchronize pull request #5530 (Introduce PolySetRenderer and add support for wireframe overlay) https://github.com/openscad/openscad/pull/5530

17:45 <gbruno> [github] kintel pushed 8 modifications (Calculate edge color from current face color) https://github.com/openscad/openscad/commit/923a5fa84cfd0ba9c21f2ff5907b0bb9169c2a3a

17:53 <gbruno> [github] kintel pushed 7 modifications (Calculate edge color from current face color) https://github.com/openscad/openscad/commit/1faeeee817441d4d35e87d17c36b2dc02dfbabb6

17:59 <gbruno> [github] kintel opened pull request #5674 (Use VBO colors for ViewEdges shader instead of uniforms.) https://github.com/openscad/openscad/pull/5674

18:41 <gbruno> [github] FourCinnamon0 opened issue #5675 (Color inheritance glitchyness on sibling geometries) https://github.com/openscad/openscad/issues/5675

18:41 <gbruno> [github] FourCinnamon0 edited issue #5675 (Color inheritance glitchyness on sibling geometries) https://github.com/openscad/openscad/issues/5675

18:57 <gbruno> [github] kintel closed issue #5675 (Color inheritance glitchyness on sibling geometries) https://github.com/openscad/openscad/issues/5675

19:29 <gbruno> [github] kintel pushed 11 additions 1 modifications (Add testcase for rendering edges for multi-color objects) https://github.com/openscad/openscad/commit/7caef49833e0f7ff403eb7dd4a51564caea549dd

19:29 <gbruno> [github] kintel synchronize pull request #5674 (Use VBO colors for ViewEdges shader instead of uniforms.) https://github.com/openscad/openscad/pull/5674

20:07 <gbruno> [github] kintel pushed 1 modifications (Disable test with artifacts) https://github.com/openscad/openscad/commit/8e9c4aee3fd93637285ca4aa34697a1a5e5686e7

20:07 <gbruno> [github] kintel synchronize pull request #5674 (Use VBO colors for ViewEdges shader instead of uniforms.) https://github.com/openscad/openscad/pull/5674

20:18 <gbruno> [github] kintel pushed 1 modifications (Disable test with artifacts) https://github.com/openscad/openscad/commit/34aca971723728f10ea7bbb60520f0c3c9901eaf

20:18 <gbruno> [github] kintel synchronize pull request #5674 (Use VBO colors for ViewEdges shader instead of uniforms.) https://github.com/openscad/openscad/pull/5674

21:25 <gbruno> [github] kintel pushed 1 modifications (NULLGL fix) https://github.com/openscad/openscad/commit/28e8aa389952fa87145d7360ca9374c499481e0b

21:25 <gbruno> [github] kintel synchronize pull request #5674 (Use VBO colors for ViewEdges shader instead of uniforms.) https://github.com/openscad/openscad/pull/5674

23:07 <gbruno> [github] dbyy opened issue #5676 (OpenScad v 2025.01.26 (Snap on Linux Mint) - Save File As: Can't navigate to mounted NAS locations (/mnt/...) (on NAS)) https://github.com/openscad/openscad/issues/5676