Just to clarify about the receivers: My problem is that I keep deleting the components that have receivers connected to them. Since there is no undo this makes it easy to do a lot of damage to a network, without any easy way of repairing. Currently, the only way to see if there is a receiver connected to a specific component is to select everything on the canvas.
The fancy wires are great btw. Anders On Mar 25, 3:48 pm, Anders <[email protected]> wrote: > Ok, I understand. I assumed the network was computed left to right, > one component after the other. > > It does not crash, it just takes a very long tome to redraw/rebuild. I > left it for one hour, but it was still working, so it is not a bug as > such, but it would be nice if the Clean component could fix it. > > Another thing: With receivers you can only see what components are > connected to the receiver. If you select a component, you will not be > able to see what receivers are connected from it. Could the lines to > the receiver light up also when the component the come from is > selected? > > Thanks, > Anders > > On Mar 25, 3:21 pm, David Rutten <[email protected]> wrote: > > > > > Hi Anders, > > > did it actually freeze or did it just take a long time to redraw? > > > Either way; yes and no. I can add empty path removal tools, I cannot > > add a progress indicator because I have no idea how long it will take > > or how many percent has been solved. Due to the nature of the solver, > > almost all components are solved from inside the loops of child > > components. So it might look as though Line2Pt takes over 10 seconds > > to solve itself, but it's actually waiting for Brep|Brep Intersect to > > complete. > > > By placing strategic timers in the solver I might be able to get a > > reasonable estimate for the time it takes, but it will not be > > accurate. > > > -- > > David Rutten > > [email protected] > > Robert McNeel & Associates > > > On Mar 25, 7:59 am, Anders <[email protected]> wrote: > > > > Hi, > > > > I believe I found another bug: > > > > Grasshopper freezes when a stream of about 1000 straight two-point > > > lines are connected to the Parameter Viewer component. It comes from a > > > Clean component, so it does not have any nulls. But the Clean > > > component does not remove unused tree paths so the tree ended up > > > having above 1 million paths, nearly all of which are empty. > > > Flattening the structure would remove the structure completely, and > > > that is not what I need. Could the Clean component have an option to > > > remove unused paths? > > > > I wish there was some kind of progress indicator when the solution is > > > rebuilding. I have a big grasshopper network that takes about 30 > > > seconds to rebuild, so a way of seeing what components take the most > > > time would be useful. Maybe each component could light up while it is > > > being rebuilt/computed. That way you could see the progress flow > > > through the network. > > > > Anders > > > > On Mar 24, 7:19 am, David Rutten <[email protected]> wrote: > > > > > Hi visose, > > > > > no, it's something to do with auto-insertion routines. > > > > I need to look long and hard at this and try to come up with better > > > > null-insertion logic. > > > > > -- > > > > David Rutten > > > > [email protected] > > > > Robert McNeel & Associates > > > > > On Mar 24, 12:08 am, visose <[email protected]> wrote: > > > > > > I think there's a bug on the "clean tree" component. The output seems > > > > > to have cleaned the <null> items but the components connected to it > > > > > seem to inherit the original list of > > > > > values:http://grasshopper3d.googlegroups.com/web/cleantreebug.jpg > > > > > > On Mar 23, 2:09 pm, David Rutten <[email protected]> wrote: > > > > > > > Revision 7 is now available for download. This releases fixes a > > > > > > Crash > > > > > > bug with baking parameters that contain <null> items. > > > > > > > Installer:http://download.mcneel.com/s3/mcneel/plug-in/beta/en/grasshopper_wip_... > > > > > > Zip > > > > > > file:http://download.mcneel.com/s3/mcneel/plug-in/beta/en/grasshopper_wip_... > > > > > > > Fixes: > > > > > > - Baking parameters with null items used to crash, this is fixed. > > > > > > - Assigning On3dVectors and planar OnPolylines in Script components > > > > > > would result in Points and Planes respectively, this is fixed. > > > > > > > Features: > > > > > > - New wire display mode (option in View menu) > > > > > > - Drag+Drop of ghx and gh files is now handled > > > > > > - Pointlist Closest Point Component. > > > > > > > -- > > > > > > David Rutten > > > > > > [email protected] > > > > > > Robert McNeel & Associates
