wpwrak has quit [Read error: Connection reset by peer]
wpwrak has joined #solvespace
<GitHub>
[solvespace] wpwrak opened pull request #169: New CLI command "dump" to load and then save a .slvs, to refresh assemblies (master...dump-to-refresh) https://github.com/solvespace/solvespace/pull/169
<wpwrak>
hmm, can a group become detached from a workplane ? e.g., when the geometry of the underlying part that provided the reference point for "sketch in new workplane" changed ?
<wpwrak>
mmh. or maybe not. getting strange effects with distances.
<whitequark>
in the sense of someone in an amphetamine psychosis being detached from reality, rather than in the sense of a button being detached from a shirt
<wpwrak>
(detached) hmm, as long as it's reversible, ...
<whitequark>
not necessarily easily reversible.
<whitequark>
well.
<whitequark>
everything is reversible as long as you check your files into VCS.
<wpwrak>
;-) the problems begin when you build on top of something and then, days later, realize that something down there got irreversibly loose
<wpwrak>
that's actually the constant fear i have: that something like this happens by accident
<whitequark>
right, so if you never delete anything from an imported sketch, you'll never break anything downstream
<wpwrak>
oh, i could delete things from an imported (assembled) sketch ? that's an ability that may be good to avoid having ;-)
<wpwrak>
especially if it could be exercised by accident
<whitequark>
hm? of course you can. just open the file you've imported and delete things.
<whitequark>
s/imported/linked/
<whitequark>
linking a file doesn't affect it in any way, nor could it
<wpwrak>
ah, downstream in that sense. right.
<wpwrak>
could slvs issue a warning if it loses something that way, when loading the downstream part ? so that one can revert or repair in a timely manner ?
<whitequark>
it does, of course, the usual "I've deleted some stuff that depended on now-deleted stuff"
<whitequark>
you can't undo that when it happens when loading the file, of course
<wpwrak>
well, by reverting the upstream change (in vcs)
<whitequark>
yes
<wpwrak>
(the usual) good. since i haven't been greeted by something like then when loading, that means that this sort of accident hasn't happened yet. another sigh of relief :)
<wpwrak>
hmm, if my cylindrical items (as STL) are very non-round, should changing the "export chord tolerance" on the part that assembles everything help ? because, it doesn't seem to.
<whitequark>
mmh, I don't recall.
<whitequark>
but note that export chord tolerance setting is global.
<whitequark>
actually, hang on, I think you've spotted a fairly nasty bug...
<wpwrak>
:)
<whitequark>
a semantic one, that is, not a coding issue
<wpwrak>
oh, that "global" really is. ~/.config/solvespace/settings.json
<whitequark>
indeed
<whitequark>
(that file is not used by the CLI, btw
<wpwrak>
good :) ah, and at the CLI i can set my own tolerance. excellent.