whitequark changed the topic of #solvespace to: SolveSpace--parametric 2d/3d CAD · latest version 2.3 · http://solvespace.com · code at https://github.com/solvespace/solvespace · logs at https://irclog.whitequark.org/solvespace
cr1901_modern has joined #solvespace
_whitelogger has joined #solvespace
_whitelogger has joined #solvespace
georges-duperon has joined #solvespace
<georges-duperon> Hi all, trying out Solvespace here — so far it seems great aside from some occasional crash.
<georges-duperon> I'm trying to change the style of some lines in a sketch, but I didn't find anything about that on the web, and can't see how in the interface.
<whitequark> georges-duperon: please report all crashes, fixing them is very high priority.
<whitequark> as for the style. right-click on the line, Assign to Style -> Newly Created Custom Style (or what you have).
<georges-duperon> whitequark: Okay, I'll do that next time it occurs :) Is the forum the right place for bugs?
<whitequark> no
<georges-duperon> whitequark: Ah, indeed. Thanks a lot for the right-click → Assign to Style, that's exactly what I needed!
<wpwrak> grr. chirality really sucks. just noticed that a cut-out had flipped sides with the thing that goes into it. for no apparent reason :(
<whitequark> yeah, the solver doesn't really make any guarantees about it.
<wpwrak> ah well, another chance to tweak print parameters :) i found a really important one: the flow multiplier. seems that cura used only 3/4 of the flow needed. that explains quite a number of print issues ... :)
seb_kuzm1nsky has joined #solvespace
seb_kuzminsky has quit [Ping timeout: 240 seconds]
seb_kuzm1nsky is now known as seb_kuzminsky
<georges-duperon> I'm making an updated solvespace package for my distribution (NixOS), using the latest git revision on master branch.
<georges-duperon> When built with cmake -DCMAKE_BUILD_TYPE=Release, the bnechmarks are built too, but I get this error (only for the benchmarks):
<georges-duperon> no matching function for call to ‘SolveSpace::SolveSpaceUI::LoadFromFile(std::__cxx11::string&)
<georges-duperon> I feel that an include_directories() is missing in bench/CMakeLists.txt, but I'm not sure about which one.
<georges-duperon> whitequark: any guess?
<whitequark> georges-duperon: it's broken
<GitHub> [solvespace] whitequark pushed 2 new commits to master: https://github.com/solvespace/solvespace/compare/5744d1d599df...acc25ecd571e
<GitHub> solvespace/master acc25ec whitequark: Fix toolbar height after 5744d1d5.
<GitHub> solvespace/master ca2aad7 whitequark: Remove the "style → background image" feature.
<georges-duperon> Oh, so I should disable -DCMAKE_BUILD_TYPE?
<whitequark> no
<GitHub> [solvespace] whitequark pushed 1 new commit to master: https://github.com/solvespace/solvespace/commit/911c67b2d8643d64f546d5fca7a64a2740cd4ba1
<GitHub> solvespace/master 911c67b whitequark: Fix benchmark harness after e2e74762.
<georges-duperon> whitequark: Oh, thanks :D
<travis-ci> solvespace/solvespace#397 (master - 911c67b : whitequark): The build passed.
<travis-ci> solvespace/solvespace#396 (master - acc25ec : whitequark): The build passed.
<GitHub> [solvespace] virtualritz opened issue #212: harness.cpp fails to build on OS X https://github.com/solvespace/solvespace/issues/212
<07EAAJS9V> [solvespace] whitequark closed issue #212: harness.cpp fails to build on OS X https://github.com/solvespace/solvespace/issues/212
<5EXAAMFSS> [solvespace] whitequark commented on issue #212: Already fixed in master. https://github.com/solvespace/solvespace/issues/212#issuecomment-287394527
<georges-duperon> whitequark: The build worked fine for me with 911c67b. Thanks again!
<GitHub> [solvespace] jsmaniac opened issue #213: Text boxes are garbled during editing https://github.com/solvespace/solvespace/issues/213
<GitHub> [solvespace] jsmaniac opened issue #214: Memory leak https://github.com/solvespace/solvespace/issues/214
<GitHub> [solvespace] whitequark commented on issue #213: > fltk-1.3.3... https://github.com/solvespace/solvespace/issues/213#issuecomment-287408169
<GitHub> [solvespace] jsmaniac closed issue #213: Text boxes are garbled during editing https://github.com/solvespace/solvespace/issues/213
<GitHub> [solvespace] whitequark commented on issue #214: > Scroll down and click "Create user style"... https://github.com/solvespace/solvespace/issues/214#issuecomment-287409441
<GitHub> [solvespace] whitequark commented on issue #213: > I had updated an existing recipe for my OS, and solvespace 2 used FLTK. I should remove it from the dependencies.... https://github.com/solvespace/solvespace/issues/213#issuecomment-287409760
<GitHub> [solvespace] jsmaniac opened issue #215: File→Save and File→Save As… crash SolveSpace https://github.com/solvespace/solvespace/issues/215
<GitHub> [solvespace] jsmaniac commented on issue #214: Yes, sorry, I meant "create a new custom style". I'll try with valgrind later (hopefully this weekend). https://github.com/solvespace/solvespace/issues/214#issuecomment-287410312
<GitHub> [solvespace] whitequark commented on issue #215: This seems like a NixOS compatibility issue. Exactly where does it crash? See https://github.com/solvespace/solvespace/blob/master/CONTRIBUTING.md#debugging-a-custom-build for instructions on how to gather a backtrace. https://github.com/solvespace/solvespace/issues/215#issuecomment-287410479
<GitHub> [solvespace] whitequark commented on issue #215: Actually, you've mentioned that the property browser window did not instantly appear. What's happening is I'm calling `show_all()` right away on that window. If GTK does the same, and then expects the window to be realized, and it's not, then it will probably die dereferencing a null pointer or something like that. https://github.com/solvespace/solvespace/issues/215#issuecomment-287412183
<GitHub> [solvespace] whitequark commented on issue #215: Actually, you've mentioned that the property browser window did not instantly appear. What's happening is I'm calling `show_all()` right away on that window. If GTK does the same, and then expects the window to be realized, and it's not, then it will probably die dereferencing a null pointer or something like that. https://github.com/solvespace/solvespace/issues/215#issuecomment-287412183
<GitHub> [solvespace] jsmaniac commented on issue #215: It turns out the browser window was just hiding behind the main window (it seems like the "foreground window" property is not taken into account, perhaps because the main window appears *after* the browser window. Even if I move the main window to the side, and bring the browser window into focus, it goes to the back as soon as focus goes to the main window. After pressing tab twice, the browser window
<GitHub> [solvespace] whitequark commented on issue #215: > Even if I move the main window to the side, and bring the browser window into focus, it goes to the back as soon as focus goes to the main window. After pressing tab twice, the browser window correctly stays on top even when the main window has the focus).... https://github.com/solvespace/solvespace/issues/215#issuecomment-287414109
<GitHub> [solvespace] jsmaniac commented on issue #214: An initial run of valgrind spits out a plethora of warnings etc.... https://github.com/solvespace/solvespace/issues/214#issuecomment-287418101
<GitHub> [solvespace] jsmaniac commented on issue #214: An initial run of valgrind spits out a plethora of warnings etc.... https://github.com/solvespace/solvespace/issues/214#issuecomment-287418101
<GitHub> [solvespace] whitequark commented on issue #214: A lot of warnings comes from GTK. It seems to be rather sloppily written, and it's nearly impossible to produce a decent suppression list (I tried).... https://github.com/solvespace/solvespace/issues/214#issuecomment-287418392
<GitHub> [solvespace] jsmaniac commented on issue #214: An initial run of valgrind spits out a plethora of warnings etc.... https://github.com/solvespace/solvespace/issues/214#issuecomment-287418428
<GitHub> [solvespace] whitequark commented on issue #214: > ==16793== 4,841,661 (56 direct, 4,841,605 indirect) bytes in 1 blocks are definitely lost in loss record 13,472 of 13,472... https://github.com/solvespace/solvespace/issues/214#issuecomment-287419653
<GitHub> [solvespace] whitequark commented on issue #214: > ==16793== 4,841,661 (56 direct, 4,841,605 indirect) bytes in 1 blocks are definitely lost in loss record 13,472 of 13,472... https://github.com/solvespace/solvespace/issues/214#issuecomment-287419653
<GitHub> [solvespace] jsmaniac commented on issue #214: Sorry, I'm rarely ever coding in C/C++, so I'm not used to valgrind. I tried with `--tool=massif`, in the graph below the first ramping up is when I started solvespace, then I left it rest for a short while (the flat section at the beginning), then I opened the colour picker (the second, more steady upward slope). I took screenshots of the green, turquoise and purple blocks on the last time frame.... 
<GitHub> [solvespace] jsmaniac commented on issue #215: No, that patch didn't change anything (I tried adding `TW->set_transient_for(*GW);` after the `GW->show_all();`, still not good). I wouldn't worry about the initial display of the browser window, though, as it is most likely a problem with my window manager, with a simple workaround (press tab twice).... https://github.com/solvespace/solvespace/issues/215#issuecomment-287436674
georges-duperon has quit [Ping timeout: 240 seconds]
georges-duperon has joined #solvespace