<GitHub>
[solvespace] whitequark commented on issue #148: And on GTK/Cocoa PaintGraphics redraws immediately. Any fix that makes the platforms diverge isn't the right fix, of course because then you and I will see different bugs. https://github.com/solvespace/solvespace/issues/148#issuecomment-270297643
mumptai has quit [Remote host closed the connection]
Guest98666 is now known as lineprinter
mumptai has joined #solvespace
<dmos>
i have a two solvespace files, first one imports the second one. how can I constrain second one's size based on first one's size? for example given two segments one in the root file and second in the imported one, equal length constraint says unsolvable.
<dmos>
constraint fails when i'm trying to scale down the imported drawing. my use case is that i have a relatively complex component, whose size should be relative to an encompassing component. it would be ideal to not have to precalculate the size of the complex component that I import by hand.
<whitequark>
you can't
<whitequark>
the imported files are imported as a single piece
<dmos>
i can think of having a global scale file, that has the root dimensions on it in reference segments and have that imported in every component. are there other ways?
<d42>
there was a a fork with commits for named variables in files/comments somewhere but i'm not sure what happened ,-,
<whitequark>
the fork is still somewhere out there. the code quality is not particularly good.
<d42>
it was pretty bad, yes
<whitequark>
eventually I'll get to integrating parametric hierarchical sketches
<whitequark>
or rather, implementing
<whitequark>
but there are serious changes that must happen before that
<dmos>
would that be a useful feature for you as habitual users of solvespace?
<d42>
since i use solvespace mainly for lasercutting plywood
<d42>
and any thickness change results in random constraint changes all over the place :v
<d42>
but i guess i can keep separate slvs with my plywood system of units :v
<dmos>
i've made the central scale file, now i'm importing it in the component files and trying bump up the imported group from last to first. is it as simple as cut-copy accordingly in the slvs file with a text editor?
<dmos>
or is there a better way to rearrange the groups?
<d42>
none that i'm aware of ,_,
<whitequark>
the reason it isn't exposed in the UI is there's no guarantee that won't delete half of your entities
<dmos>
so, uhm, can i bump up the imported group by hand? or is it too complicated.
<whitequark>
you can try, sure
<whitequark>
I would delete and reimport, personally
<dmos>
for example the groups i just placed after the references group has this attribute `Group.h.v=00000009`. Does this index have to be changed?
<whitequark>
dunno
<whitequark>
that's why I would delete and reimport
<whitequark>
the format was never designed for poking around
<dmos>
yeah, no effect. i'll resketch.
<dmos>
thanks
mumptai has quit [Remote host closed the connection]