| 00:03.42 | wpwrak | or cylindrical ? like this critter: http://www.digikey.com/product-detail/en/keystone-electronics/5203/36-5203-ND/316367 |
| 00:04.01 | wpwrak | may be a bit costly on the gfx, i guess |
| 00:06.00 | whitequark | nope, and has nothing to do with gfx |
| 00:06.12 | whitequark | we don't have lofting because the NURBS backend doesn't support it |
| 00:09.12 | wpwrak | ah, pity. well, a minor cosmetic detail at this point. |
| 02:44.56 | *** join/#qi-hardware uwe_ (~uwe_@ipservice-092-217-108-010.092.217.pools.vodafone-ip.de) |
| 05:09.30 | *** join/#qi-hardware DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 06:56.45 | *** join/#qi-hardware erichvk (~esh@ppp118-210-91-59.lns20.adl2.internode.on.net) |
| 07:22.06 | *** join/#qi-hardware sandeepkr_ (~Sandeepkr@103.49.155.114) |
| 09:07.06 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 10:35.45 | *** join/#qi-hardware rockyh (~lgking@unaffiliated/rockyh) |
| 11:07.36 | *** join/#qi-hardware Nik05 (~Nik05@unaffiliated/nik05) |
| 11:35.23 | *** join/#qi-hardware sandeepkr_ (~Sandeepkr@103.49.155.114) |
| 12:03.30 | *** join/#qi-hardware dandon (~dandon@185.16.52.186) |
| 12:32.07 | *** join/#qi-hardware sandeepkr_ (~Sandeepkr@103.49.155.114) |
| 13:15.07 | *** join/#qi-hardware sandeepkr__ (~Sandeepkr@103.49.155.114) |
| 13:16.33 | *** join/#qi-hardware rodgort` (~rodgort@68.ip-149-56-14.net) |
| 14:19.31 | *** join/#qi-hardware sandeepkr (~Sandeepkr@103.49.155.114) |
| 16:27.04 | *** join/#qi-hardware bzb (~bzb@135-23-193-53.cpe.pppoe.ca) |
| 16:57.00 | *** join/#qi-hardware pcercuei (~paul@137.71.226.54) |
| 18:44.39 | *** join/#qi-hardware pcercuei (~pcercuei@92.177.36.45) |
| 18:46.21 | *** join/#qi-hardware sandeepkr_ (~Sandeepkr@103.49.155.114) |
| 20:46.38 | 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.14 | 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.09 | whitequark | wpwrak: yes, you can |
| 20:50.21 | whitequark | first, constrain a line to have the same length as the arc |
| 20:50.28 | whitequark | then use construction as usual |
| 20:50.34 | wpwrak | oh :) |
| 20:51.37 | wpwrak | kewl |
| 20:52.29 | wpwrak | i guess i couldn't do that for the whole cable (line + arc + line) , could i ? |
| 20:53.03 | whitequark | nope but you could do three vertical lines... |
| 20:53.32 | whitequark | there's , of course |
| 20:53.38 | whitequark | https://github.com/solvespace/solvespace/issues/77 |
| 20:56.25 | wpwrak | yup :) |
| 20:57.43 | 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.43 | whitequark | yup |
| 20:58.55 | whitequark | and we're going to make the solver even better |
| 20:59.08 | whitequark | right now it can choke on really large sketches, but integrating Eigen should solve that |
| 20:59.16 | whitequark | (solve, geddit) |
| 21:02.44 | wpwrak | kewl |
| 21:04.41 | 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.31 | whitequark | wpwrak: hum. |
| 21:07.37 | whitequark | did that break *again*? :/ |
| 21:07.38 | wpwrak | meh. sometimes it seems to take the palette field i right-click on. but not always. |
| 21:07.49 | wpwrak | ;-) |
| 21:07.53 | whitequark | ARGH |
| 21:07.55 | whitequark | it did |
| 21:07.59 | wpwrak | :) |
| 21:08.02 | whitequark | please file a bug about it, gtk is acting up... |
| 21:08.09 | whitequark | I swear I fixed this like three times already |
| 21:09.44 | 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.16 | whitequark | yeah I just checked that one on master |
| 21:17.58 | wpwrak | fresh bug: https://github.com/solvespace/solvespace/issues/154 |
| 21:19.41 | 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.12 | whitequark | wpwrak: can you override https://developer.gnome.org/gtkmm/3.22/classGtk_1_1Widget.html#a7697fa829dc749a19347d27f9c7f5c66 |
| 21:22.21 | whitequark | then uhhh print the event in gdb or something |
| 21:22.26 | whitequark | the window doesn't like *Something* |
| 21:23.47 | wpwrak | btw, here's the OLED module: https://gitlab.com/anelok/anelok/blob/master/me4/oled.slvs |
| 21:39.22 | whitequark | oh, that's not a raw sketch... |
| 21:40.14 | whitequark | wpwrak: neat |
| 21:40.28 | whitequark | btw, have you appreciated the stippled hidden line mode yet? |
| 21:42.25 | wpwrak | yes, that one is quite nice. didn't need it here, but i found it useful when experimenting with unions and differences. |
| 22:39.17 | *** part/#qi-hardware rockyh (~lgking@unaffiliated/rockyh) |
| 22:54.48 | whitequark | wpwrak: that one took quite a lot of effort to get right :D |
| 23:19.49 | 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.51 | 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.35 | wpwrak | DocScrutinizer05: you need solvespace to visualize it |
| 23:20.54 | DocScrutinizer05 | meh, obviously konqueror tries to load it |
| 23:21.38 | whitequark | DocScrutinizer05: unfortunately solvespace files don't have any leading 0-s |
| 23:21.39 | 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.45 | whitequark | so all kinds of crap try to treat them as text |
| 23:21.46 | wpwrak | valiantly, the neanderthal raises his stick, threatening the approaching tanks ;-) |
| 23:21.51 | whitequark | lol |
| 23:22.49 | DocScrutinizer05 | lol, don't get me started about chromium |
| 23:23.18 | whitequark | gives DocScrutinizer05 a wget |
| 23:23.26 | whitequark | an elegant weapon, for a more civilized age |
| 23:23.29 | DocScrutinizer05 | I just killed a chromium process that aze 3.2GB of RAM |
| 23:23.37 | whitequark | I literally have that as a cronjob |
| 23:23.38 | DocScrutinizer05 | ate* |
| 23:23.57 | whitequark | for some reason chromium leaks *GPU memory* on my machine, with disastrous results |
| 23:24.08 | whitequark | I haven't even previously considered that as possible |
| 23:24.11 | DocScrutinizer05 | seems same here |
| 23:24.29 | wpwrak | "aze", pronounced "assed" |
| 23:24.51 | whitequark | was it the --type=gpu-process one? |
| 23:25.00 | 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.20 | DocScrutinizer05 | can't tell anymore |
| 23:25.31 | whitequark | then not |
| 23:26.17 | 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.49 | whitequark | btw did you know you can type "badidea" at any chromium error screen to bypass it |
| 23:26.53 | whitequark | even the unbypassable ones |
| 23:27.09 | wpwrak | ;-)) |
| 23:27.21 | whitequark | there's a joke about software somewhere here but I'm too sad to make it |
| 23:28.01 | 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.27 | DocScrutinizer05 | 66MB |
| 23:29.58 | whitequark | I see you also have systemd there |
| 23:30.44 | DocScrutinizer05 | http://wstaw.org/m/2017/01/13/plasma-desktopj17764.png |
| 23:31.04 | DocScrutinizer05 | yeah, could puke over the Alps about that |
| 23:31.55 | DocScrutinizer05 | at least you can't blame me I'm a hater not knowing what he loves to hate |
| 23:32.29 | DocScrutinizer05 | I hate systemd *be3cause* it's on my system |
| 23:33.10 | DocScrutinizer05 | if there was an option to not have it, I'd absolutely ignore the whole pile of shit |
| 23:38.55 | wpwrak | repent, and install devuan :) |
| 23:42.01 | 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.34 | DocScrutinizer05 | wpwrak: even devuan can't provide a desktop like gnome or kde without systemd anymore |
| 23:46.16 | 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.28 | DocScrutinizer05 | like mad, not med |
