00:00 <gbruno> [github] t-paul closed pull request #5111 (Fix initial GUI setup.) https://github.com/openscad/openscad/pull/5111

00:00 <gbruno> [github] t-paul pushed 2 modifications (Merge pull request #5111 from openscad/fix-initial-gui Fix initial GUI setup.) https://github.com/openscad/openscad/commit/97184930d36d6d5cb126b5e0e0cd5ca3c606c05f

06:29 <gbruno> [github] haikusw opened issue #5116 (Viewport-Control widget can be made too narrow; tab order broken.) https://github.com/openscad/openscad/issues/5116

06:32 <gbruno> [github] haikusw opened pull request #5117 (Add tab order back in. Switch fixed width for dynamic. fixes #5116) https://github.com/openscad/openscad/pull/5117

06:34 <gbruno> [github] haikusw edited pull request #5117 (Viewport-Control widget: Limit width to at least dynamic minimum size of widget. Add tab order back in. Fixes #5116) https://github.com/openscad/openscad/pull/5117

06:49 <gbruno> [github] t-paul closed issue #5116 (Viewport-Control widget can be made too narrow; tab order broken.) https://github.com/openscad/openscad/issues/5116

17:22 <JordanBrown> teepee, InPhase: WRT font selection and system fonts, note that the underlying fontconfig library is intended to let you select fonts by describing them rather than by giving specific names. Of course that doesn't help when you want to choose between two different fonts that differ only in Il1, but it shouldn't be forgotten. If you want portable programs, it's probably best to specify your font in those terms rather than by specific names.

17:23 <teepee> you *can* but names are a valid search criteria

17:23 <teepee> so if you need a special glyph, you may need special fonts

17:23 <JordanBrown> Sure

17:23 <teepee> the sample field specifically disables font substitution so Qt is not replacing glyphs from other fonts which is the default

17:24 <JordanBrown> but as a future project for somebody, it might be good to have a "search by characteristic" UI, that narrowed down to the fonts on your system that match, and when the match is small enough you would copy the description rather than the name.

17:24 <JordanBrown> kind of like xfontsel

17:26 <JordanBrown> but it sounds like what you're doing is good stuff.

17:47 <teepee> I guess having such extendes search options is fine. I'm always a bit hesitant leaking the internal logic, but probably that ship has sailed anyway, so it's font = <fontconfig-search-spec>

17:51 <JordanBrown> Right. On the one hand, that ties us to fontconfig, but on the other hand it allows *not* tying a model to a specific font.

17:53 <teepee> yep, there's never the a single simple answer :)

17:54 <JordanBrown> Actually, to be more precise, it ties us to fontconfig's specification language.

17:54 <teepee> true, there would be the theoretical option to use a different backend and translating the specs

17:55 <teepee> so far fontconfig seems fine on all the supported platform, so the worry is not very big anymore

18:58 <gbruno> [github] gsohler synchronize pull request #5113 (Linextrude) https://github.com/openscad/openscad/pull/5113