00:03 <wpwrak> or cylindrical ? like this critter: http://www.digikey.com/product-detail/en/keystone-electronics/5203/36-5203-ND/316367

00:04 <wpwrak> may be a bit costly on the gfx, i guess

00:06 <whitequark> nope, and has nothing to do with gfx

00:06 <whitequark> we don't have lofting because the NURBS backend doesn't support it

00:09 <wpwrak> ah, pity. well, a minor cosmetic detail at this point.

20:46 <wpwrak> whitequark: hmm .. can i use the length of an arc as constraint ? without having to manually calculate the radius ? i.e., for an FPC on a display module, i basically have the real-life constraint FPC_on_module + pi * bend_radius + FPC_to_connector = 36 mm (or similar)

20:47 <wpwrak> having to manage a sum of length isn't so bad, but manually converting the radius is kinda inconvenient. any nice way to do this ?

20:50 <whitequark> wpwrak: yes, you can

20:50 <whitequark> first, constrain a line to have the same length as the arc

20:50 <whitequark> then use construction as usual

20:50 <wpwrak> oh :)

20:51 <wpwrak> kewl

20:52 <wpwrak> i guess i couldn't do that for the whole cable (line + arc + line) , could i ?

20:53 <whitequark> nope but you could do three vertical lines...

20:53 <whitequark> there's , of course

20:53 <whitequark> https://github.com/solvespace/solvespace/issues/77

20:56 <wpwrak> yup :)

20:57 <wpwrak> but the sequence of lines also worked. amazing ! the solver can be surprisingly robust. as long as i don't bump into a chirality trap, it behaves really well

20:58 <whitequark> yup

20:58 <whitequark> and we're going to make the solver even better

20:59 <whitequark> right now it can choke on really large sketches, but integrating Eigen should solve that

20:59 <whitequark> (solve, geddit)

21:02 <wpwrak> kewl

21:04 <wpwrak> hmm, color selection is confusing. first, the color chooser overlay is hard to distinguish from the dialog it overlays. second, it seems that i can only choose by rgb value, not by clicking on a color or moving around in the huw (?) etc. area

21:07 <whitequark> wpwrak: hum.

21:07 <whitequark> did that break *again*? :/

21:07 <wpwrak> meh. sometimes it seems to take the palette field i right-click on. but not always.

21:07 <wpwrak> ;-)

21:07 <whitequark> ARGH

21:07 <whitequark> it did

21:07 <wpwrak> :)

21:08 <whitequark> please file a bug about it, gtk is acting up...

21:08 <whitequark> I swear I fixed this like three times already

21:09 <wpwrak> for all i comment on, please keep always in mind that i'm at the version before the gtkmm 3.22 requirement. so i'll eventually complain about things you've already fixed.

21:17 <whitequark> yeah I just checked that one on master

21:17 <wpwrak> fresh bug: https://github.com/solvespace/solvespace/issues/154

21:19 <wpwrak> regarding the DISPLAY_TEXTWND, what shall we do ? i looked around a little for anything obvious that would cause the window to disappear right after opening it, but couldn't find anything. in any case, this doesn't seem to cause any other issue (crash or such), and once i get it to stay, it seems to behave normally

21:22 <whitequark> wpwrak: can you override https://developer.gnome.org/gtkmm/3.22/classGtk_1_1Widget.html#a7697fa829dc749a19347d27f9c7f5c66

21:22 <whitequark> then uhhh print the event in gdb or something

21:22 <whitequark> the window doesn't like *Something*

21:23 <wpwrak> btw, here's the OLED module: https://gitlab.com/anelok/anelok/blob/master/me4/oled.slvs

21:39 <whitequark> oh, that's not a raw sketch...

21:40 <whitequark> wpwrak: neat

21:40 <whitequark> btw, have you appreciated the stippled hidden line mode yet?

21:42 <wpwrak> yes, that one is quite nice. didn't need it here, but i found it useful when experimenting with unions and differences.

22:54 <whitequark> wpwrak: that one took quite a lot of effort to get right :D

23:19 <DocScrutinizer05> damn, https://gitlab.com/anelok/anelok/blob/master/me4/oled.slvs again leaves me with a red screen, though I "solved" that for other gitlab crap already

23:19 <wpwrak> naw, i found one bug and learned quite a bit about how far i can take the solver. so that's a good result, considering the invaluable resource of free whitequark advice :)

23:20 <wpwrak> DocScrutinizer05: you need solvespace to visualize it

23:20 <DocScrutinizer05> meh, obviously konqueror tries to load it

23:21 <whitequark> DocScrutinizer05: unfortunately solvespace files don't have any leading 0-s

23:21 <DocScrutinizer05> but it gives me the usual red screen from that friggin progress bar, just here it doesn't vanish on ptressing F5

23:21 <whitequark> so all kinds of crap try to treat them as text

23:21 <wpwrak> valiantly, the neanderthal raises his stick, threatening the approaching tanks ;-)

23:21 <whitequark> lol

23:22 <DocScrutinizer05> lol, don't get me started about chromium

23:23 <whitequark> an elegant weapon, for a more civilized age

23:23 <DocScrutinizer05> I just killed a chromium process that aze 3.2GB of RAM

23:23 <whitequark> I literally have that as a cronjob

23:23 <DocScrutinizer05> ate*

23:23 <whitequark> for some reason chromium leaks *GPU memory* on my machine, with disastrous results

23:24 <whitequark> I haven't even previously considered that as possible

23:24 <DocScrutinizer05> seems same here

23:24 <wpwrak> "aze", pronounced "assed"

23:24 <whitequark> was it the --type=gpu-process one?

23:25 <DocScrutinizer05> when I killed the process, it shown a "sorry this page had an error displaying" OWTTE in the window and offered to reload it

23:25 <DocScrutinizer05> can't tell anymore

23:25 <whitequark> then not

23:26 <wpwrak> chromium error messages tend to be almost uniquely unhelpful. almost, because the web pages they link to are a few notches worse

23:26 <whitequark> btw did you know you can type "badidea" at any chromium error screen to bypass it

23:26 <whitequark> even the unbypassable ones

23:27 <wpwrak> ;-))

23:27 <whitequark> there's a joke about software somewhere here but I'm too sad to make it

23:28 <DocScrutinizer05> http://wstaw.org/m/2017/01/13/plasma-desktopM17764.png which happily grew from 61MB to 63MB while I just watched it

23:29 <DocScrutinizer05> 66MB

23:29 <whitequark> I see you also have systemd there

23:30 <DocScrutinizer05> http://wstaw.org/m/2017/01/13/plasma-desktopj17764.png

23:31 <DocScrutinizer05> yeah, could puke over the Alps about that

23:31 <DocScrutinizer05> at least you can't blame me I'm a hater not knowing what he loves to hate

23:32 <DocScrutinizer05> I hate systemd *be3cause* it's on my system

23:33 <DocScrutinizer05> if there was an option to not have it, I'd absolutely ignore the whole pile of shit

23:38 <wpwrak> repent, and install devuan :)

23:42 <DocScrutinizer05> http://wstaw.org/m/2017/01/13/plasma-desktopC17764.png http://wstaw.org/m/2017/01/13/plasma-desktopd17764.png is the culprit

23:42 <DocScrutinizer05> wpwrak: even devuan can't provide a desktop like gnome or kde without systemd anymore

23:46 <DocScrutinizer05> anyway this chromium crap memleaks like med - and I thought that was just konqueror that has this problem, but actually konqueror doesn't memleak much, it just leaves "zombies" for each window you close

23:46 <DocScrutinizer05> like mad, not med