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 quit [Ping timeout: 260 seconds]
<whitequark> oh? what was it?
lexszero has left #solvespace [#solvespace]
<wpwrak> i guess it may be just some issue with positioning hints. haven't looked into details yet. but what i've observed so far matches the theory.
<wpwrak> what is weird is that the rate of issues dropped so dramatically, for no apparent reason. unless my mind state somehow affects window positioning :)
<wpwrak> but there could be small changes in my workflow that affect it
mifune has joined #solvespace
mifune has joined #solvespace
mifune has quit [Changing host]
<GitHub> [solvespace] Evil-Spirit commented on issue #202: @whitequark revolution axis direction parameters is created when generating lathe group... I probably made this like it was made for extrusion group but now it is obvious what this is not the right solution because we can't drive some parameters of the previous group... https://github.com/solvespace/solvespace/issues/202#issuecomment-279302003
<GitHub> [solvespace] Evil-Spirit commented on issue #202: @whitequark, This is probably bug, so we have to remake this in correct way. https://github.com/solvespace/solvespace/issues/202#issuecomment-279302050
<GitHub> [solvespace] Evil-Spirit commented on issue #199: @whitequark, When we are trying to get NormalGetExprs which is using during builing equations for same orientation, it returns projected equations when in workplane. I don't know how we should do in this case. Probably, we should restrict using pure 3d constraints when operating in workplane,, but this is not good for backward compatibility https://github.com/solvespace/solvespace/issues/199#iss
mifune has quit [Ping timeout: 260 seconds]
mifune has joined #solvespace
mifune has joined #solvespace
mifune has quit [Changing host]
<GitHub> [solvespace] whitequark commented on issue #199: @jwesthues Is the same orientation constraint intended to produce different equations when in workplane? Or is that an accident? https://github.com/solvespace/solvespace/issues/199#issuecomment-279311329
mifune has quit [Quit: Leaving]
dfgg has quit [Ping timeout: 255 seconds]
dfgg has joined #solvespace
Nerterologist has joined #solvespace
d42 has quit [Ping timeout: 240 seconds]
Nerterologist has quit [Ping timeout: 245 seconds]
dmos has quit [Quit: EliteBNC - http://www.elitebnc.net/]
dmos62 has joined #solvespace
dmos62 is now known as dmos
d42 has joined #solvespace
<GitHub> [solvespace] Evil-Spirit commented on issue #202: @whitequark, fixed here https://github.com/solvespace/solvespace/issues/202#issuecomment-279454409
dmos has left #solvespace [#solvespace]
<GitHub> [solvespace] Evil-Spirit commented on issue #199: @whitequark, fixed here. We have one more place where it can happen again: pt-on-line. What should we do with 3d entities with pt-on-line constraint in a workplane? https://github.com/solvespace/solvespace/issues/199#issuecomment-279456176
<GitHub> [solvespace] jwesthues commented on issue #199: @Evil-Spirit The geometrically obvious thing, constrain the projection of the point into the workplane to lie on the projection of the line into the workplane. That's what it did before.... https://github.com/solvespace/solvespace/issues/199#issuecomment-279463963
cr1901_modern has quit [Ping timeout: 264 seconds]
cr1901_modern has joined #solvespace