01:35 <GitHub> [solvespace] holocronweaver commented on issue #191: This was bugging me because Anaconda has done this to me before. Found the issue in the solvespace binary rpath:... https://github.com/solvespace/solvespace/issues/191#issuecomment-277873524

01:36 <GitHub> [solvespace] holocronweaver commented on issue #191: This was bugging me because Anaconda has done this to me before. Found the issue in the solvespace binary rpath:... https://github.com/solvespace/solvespace/issues/191#issuecomment-277873524

01:37 <GitHub> [solvespace] holocronweaver commented on issue #191: This was bugging me because Anaconda has done this to me before. Found the issue in the solvespace binary rpath:... https://github.com/solvespace/solvespace/issues/191#issuecomment-277873524

01:38 <GitHub> [solvespace] holocronweaver commented on issue #191: This was bugging me because Anaconda has done this to me before. Found the issue in the solvespace binary rpath:... https://github.com/solvespace/solvespace/issues/191#issuecomment-277873524

01:52 <GitHub> [solvespace] holocronweaver commented on issue #191: This was bugging me because Anaconda has done this to me before. Found the issue in the solvespace binary rpath:... https://github.com/solvespace/solvespace/issues/191#issuecomment-277873524

02:24 <GitHub> [solvespace] holocronweaver commented on issue #191: This was bugging me because Anaconda has done this to me before. Found the issue in the solvespace binary rpath:... https://github.com/solvespace/solvespace/issues/191#issuecomment-277873524

19:35 <wpwrak> whitequark: there's no way to set a different color for the points of the active group, is there ?

19:37 <wpwrak> (my screen looks like an invasion of the borg, full of little squares, scattered all over known space ;-)

20:02 <whitequark> lol

20:02 <whitequark> no, I don't think so...

20:11 <wpwrak> i already changed the hidden lines from white to light pink. makes things a lot clearer. just the points are resisting so far. futilely, i hope :)

20:21 <whitequark> mhm, I can add that option, I think

21:26 <wpwrak> that would be great. btw, this is what it looks like: http://downloads.qi-hardware.com/people/werner/slvs/an-but-meet-the-borg.png

21:27 <wpwrak> (as you can see, i now made it past the first round for the main shell. now, for subsequent parts, i can include it as an assembly, which helps processing time quite a bit :)

21:29 <wpwrak> ah, and there's another feature that would be useful: to be able to toggle the visibility of groups in assembled parts, without affecting that part. somewhat related to #80, i guess

21:31 <wpwrak> use case: you have one complex part where you use some groups for "offspring" A and other groups for "offspring" B. the ones you don't need just get in the way, and it's kinda awkward to have to switch visbility in the "parent" back and forth, depending on which offspring one is working

21:32 <wpwrak> also, if such a parent was used in a library (which you don't want to change), such a workflow would be even more inconvenient

21:34 <whitequark> (picture) have you considered disabling earlier groups?

21:34 <whitequark> hiding

21:34 <whitequark> but yeah. it's #80.

21:53 <wpwrak> you mean "show" ? yes, i use that all the time. otherwise, that point cloud would be complete unmanageable. even this one shows just a subset.