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
mifune has joined #solvespace
mifune has quit [Changing host]
mifune has joined #solvespace
mifune has quit [Ping timeout: 240 seconds]
<GitHub> [solvespace] wpwrak opened issue #192: custom style on comment causes occlusion https://github.com/solvespace/solvespace/issues/192
<GitHub> [solvespace] whitequark commented on issue #192: This is a regression in 3.0; 2.x used to draw comments, even with custom style, over all other geometry. https://github.com/solvespace/solvespace/issues/192#issuecomment-278258129
<whitequark> wpwrak: okay,
<whitequark> *.
nathan7 has quit [Ping timeout: 252 seconds]
nathan7 has joined #solvespace
nathan7_ has joined #solvespace
nathan7_ has joined #solvespace
nathan7_ has quit [Changing host]
nathan7 has quit [*.net *.split]
Pierre1 has quit [*.net *.split]
<wpwrak> whee, reverse world ! now, for some reason, TW doesn't stay at all if NOT using DISPLAY_TEXTWND, while DISPLAY_TEXTWND works as usual, i.e., not perfectly, but not 100% failure ;-) tried closing some windows, but it's not that.
<whitequark> wtf
<wpwrak> meh. now it works. actually ... it appeared at an unusual place ... lemme see if there's a pattern ...
<wpwrak> (unusual) very low on the screen
<wpwrak> grmbl. of course, now i can't reproduce the disappearance with DISPLAY_TEXTWND. some bugs cling on to life with remarkable persistence.
<whitequark> is one of your monitors larger than the other?
<wpwrak> no, same size
cr1901_modern has quit [Ping timeout: 276 seconds]
cr1901_modern has joined #solvespace
<GitHub> [solvespace] whitequark pushed 1 new commit to master: https://github.com/solvespace/solvespace/commit/f29d9d7a34adb466d9a923e037b24c9c64b68af8
<GitHub> solvespace/master f29d9d7 whitequark: GTK: run DoLater after the next main loop iteration....
<whitequark> wpwrak: I've fixed your dragging issue
<GitHub> [solvespace] whitequark commented on issue #148: Fixed in master. https://github.com/solvespace/solvespace/issues/148#issuecomment-278342869
<whitequark> was pretty subtle
<wpwrak> yes ! thanks a lot !
<wpwrak> hmm ... interesting pattern. i'm making somewhat major changes to a sketch. that sketch is used in an extrusion which is later on used in a point-on-face (?) constraint. during the changes i break the outline by first deleting a constraint and then moving a point. i.e., without deleting any lines or arcs.
<wpwrak> then i delete a distance. now it seems that slvs tries to recalculate the rest, and promptly complains about the point-on-face constraint, probably because that face no longer gets created. that error stays on until i close the outline again.
<wpwrak> interestingly, deleting the line i used to "patch" the outline doesn't bring the error back. odd.
<whitequark> sounds about what I expect
<wpwrak> but all this suggests that a "defer updating future groups during major surgery" function would be useful. referential integrity would still be preserved, but unavoidable transient issues would not be reported. besides, everything would probably be a lot faster.
<whitequark> that would be nicely doable with chiral constraints
<wpwrak> (i now get delays in the order of ten seconds for things that trigger a recalculation)
<whitequark> commercial parametric CAD packages will often give you delays on order of minutes too :p
<wpwrak> well, i can just check the following groups for chirality changes later
<whitequark> I'm really not happy with shipping a feature that breaks sketches silently
<wpwrak> display a big warning when someone uses it for the first time :)
<whitequark> or I could spend time working on chirality instead
<wpwrak> heh :)
<whitequark> you can just patch this thing in your local tree if you want it *right now*
<whitequark> anyhow because even if I agreed to implement this, you wouldn't get it today...
<wpwrak> oh, i can be patient ;)
nathan7_ is now known as nathan7
<wpwrak> by the way, my suspicion that the TW disappearance is caused by it simply ending up off-screen, and me now looking for confirmation of that theory, caused the issue to completely disappear. i wonder of that bug is reading #solvespace :)
<whitequark> lol
<wpwrak> oh, and continuous recalculation is no miracle cure. i guess, at the end of the day, you get pretty much the same whether you ignore the transient problems it finds or whether you can suppress recalculation. e.g., i got this stylish spike: http://downloads.qi-hardware.com/people/werner/slvs/spike-despite-continuous-recalculation.png
<wpwrak> (i'm actually surprised it didn't cause more confusion :)
<travis-ci> solvespace/solvespace#357 (master - f29d9d7 : whitequark): The build passed.
<GitHub> [solvespace] wpwrak opened issue #193: switch to "Anywhere in 3d" can cause confusion https://github.com/solvespace/solvespace/issues/193
<GitHub> [solvespace] whitequark commented on issue #193: The "unexpectedly" part is not actionable without a way to reproduce. In general SolveSpace switches to the free in 3d mode by itself in one case: when there isn't a workplane available. https://github.com/solvespace/solvespace/issues/193#issuecomment-278373214
<wpwrak> tricky. if i knew what causes the switch, i would probably avoid it :) is there a place i could put an abort to immediately make me aware that an automatic switch would be happening ? then i'd know what exactly i did last
mifune has joined #solvespace
mifune has joined #solvespace
mifune has quit [Changing host]
<GitHub> [solvespace] wpwrak commented on issue #193: Okay, I found one case where this happens: I have a sketch without issues (that I know of). In this sketch there is an arc with both endpoints fixed. I set the center with a point-to-point coincidence, which over-constrains the sketch and I get an error. At this point I'm still in the workplane.... https://github.com/solvespace/solvespace/issues/193#issuecomment-278387267
<GitHub> [solvespace] wpwrak commented on issue #193: The plot thickens: the "undo" also changed the group (from g01f-sk-minus-base waaay out to g02d-balance). No surprise it doesn't find my old workplane there. The group change may in turn have been caused by reporting a transient SOLVE FAILURE of the #182 type. https://github.com/solvespace/solvespace/issues/193#issuecomment-278389835
<GitHub> [solvespace] whitequark commented on issue #193: Yes, that seems likely. https://github.com/solvespace/solvespace/issues/193#issuecomment-278391855
<GitHub> [solvespace] whitequark commented on issue #193: What are the exact steps to reproduce? https://github.com/solvespace/solvespace/issues/193#issuecomment-278391993
<wpwrak> working on them ... there's even one more twist, it seems
<wpwrak> ah no, that extra twist was operator error. forgot one step.
<GitHub> [solvespace] wpwrak commented on issue #193: I put a snapshot where I stopped editing at the right moment into... https://github.com/solvespace/solvespace/issues/193#issuecomment-278398233
<wpwrak> pretty circuitous. jfk's magic bullet has nothing on that one ;-)
<whitequark> wpwrak: seems like a duplicate of #182...
<wpwrak> partially, yes. the unwelcome surprise is the switch out of the workplane, even though we're still in the same group.
<wpwrak> same group -> all the editing seems to work as before. just doesn't do the same as before.
<whitequark> I think one thing we could do is make a solver failure forcibly activate the troublesome group
<GitHub> [solvespace] whitequark commented on issue #193: Can you try this patch?... https://github.com/solvespace/solvespace/issues/193#issuecomment-278410717
<GitHub> [solvespace] wpwrak commented on issue #193: Seems to have no effect. I.e., sk-minus-base is still the active group after the "undo" and #182. https://github.com/solvespace/solvespace/issues/193#issuecomment-278414446
<GitHub> [solvespace] whitequark commented on issue #193: Sorry, incomplete patch.... https://github.com/solvespace/solvespace/issues/193#issuecomment-278415170
<wpwrak> grmbl. already at the next bug. Show Degrees of Freedom -> 100% CPU ...
<GitHub> [solvespace] wpwrak commented on issue #193: Now it works, thanks ! However, it makes #182 also a little weirder:... https://github.com/solvespace/solvespace/issues/193#issuecomment-278427132
<wpwrak> those intertwined bugs are fun ;-) (at least once you know what's going on)
<wpwrak> hmm, seems that "Show Degrees of Freedom" never shows anything in a group that is an assembly (without other things in it). bug or feature ?
<whitequark> wpwrak: sounds vaguely like a bug
<wpwrak> filing an issue ...
mifune has quit [Ping timeout: 245 seconds]
<wpwrak> #103 will be such a big leap forward. just gave up on converting a circle into a D shape. no matter what i do, i can't cheat death (deleting the circle taking numerous other groups with it). fortunately, it's not a major issue to have that circle/cylinder there.