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
sklv1 has quit [Remote host closed the connection]
sklv1 has joined #solvespace
<_whitenotifier-f> [solvespace/solvespace] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/JfQ21
<_whitenotifier-f> [solvespace/solvespace] phkahler 4c00bde - Circles have no less than 16 segments
<_whitenotifier-f> [solvespace/solvespace] whitequark pushed 1 commit to master [+0/-0/±2] https://git.io/JfQ2M
<_whitenotifier-f> [solvespace/solvespace] phkahler c876104 - Make sure circles have at least 16 segments.
<_whitenotifier-f> [solvespace] Error. The Travis CI build could not complete due to an error - https://travis-ci.org/github/solvespace/solvespace/builds/698128738?utm_source=github_status&utm_medium=notification
<_whitenotifier-f> [solvespace/solvespace] whitequark pushed 1 commit to master [+0/-0/±24] https://git.io/JfQ2y
<_whitenotifier-f> [solvespace/solvespace] phkahler 3d51b39 - Change default chord tolerance (to 0.1%) and maximum segments (to 20).
<_whitenotifier-f> [solvespace] whitequark commented on pull request #627: default chordTol=0.1% max segments=20 - https://git.io/JfQ2S
<_whitenotifier-f> [solvespace] whitequark closed pull request #627: default chordTol=0.1% max segments=20 - https://git.io/JfXNY
<_whitenotifier-f> [solvespace] Success. AppVeyor build succeeded - https://ci.appveyor.com/project/whitequark/solvespace/builds/33507587
<_whitenotifier-f> [solvespace] Failure. AppVeyor build failed - https://ci.appveyor.com/project/whitequark/solvespace/builds/33507591
<_whitenotifier-f> [solvespace] Success. AppVeyor build succeeded - https://ci.appveyor.com/project/whitequark/solvespace/builds/33507638
miek has quit [Ping timeout: 246 seconds]
miek has joined #solvespace
leorat has quit [Quit: Leaving]
<flip214> I tried to make the cross-beams by clicking on a border edge and one of the post-corners; that didn't result in a volume.
<flip214> Then I tried to split the border edge up; that resulted in bad edges again. With ---border>>----A---B---Corner and A/B being the newly added points,
<flip214> intersecting the border with the edges coming to A and B gave me a border up to A, an edge AB, and another edge A-Corner (instead of B-Corner)
<flip214> is that a bug in 2.3+repack1-4 or am I just holding it wrong? Seems to happen to me every time I try to intersect lines with each other.
<flip214> Even using separate construction lines and intersecting them with the corner edge gave me such duplicated edges.
mauz555 has joined #solvespace
sklv1 has quit [Quit: quit]
mauz555 has quit []
leorat has joined #solvespace
tjader has joined #solvespace
<tjader> Is there a newer Windows build available other than 2.3?
<tjader> Thanks, I'll check it out
<tjader> I've recently got a 3d printer and am trying it cad programs, so far solvespace is my favorite
<whitequark> nice!
leorat has quit [Read error: Connection reset by peer]
<tjader> It's complaining about a missing dll, vcomp140d.dll
<whitequark> ah, I should fix that
<whitequark> can you file an issue so I remember to?
<tjader> Sure
<tjader> Is there some workaround I can do for now?
<whitequark> yes
<tjader> Do I have to follow the suggested format on the issue or is a short explanation enough?
<_whitenotifier-f> [solvespace] RodrigoTjader opened issue #631: Windows artifact complains about vcomp140d.dll - https://git.io/Jf7TJ
<tjader> Oops, submitted it by mistake
<_whitenotifier-f> [solvespace] RodrigoTjader edited issue #631: Windows artifact complains about vcomp140d.dll - https://git.io/Jf7TJ
<tjader> That other link you sent also didn't work
<whitequark> short explanation is enough
<whitequark> ugh, probably not old enough
<whitequark> one moment
<_whitenotifier-f> [solvespace] whitequark commented on issue #631: Windows artifact complains about vcomp140d.dll - https://git.io/Jf7Ta
<tjader> That one runs, thamks