Hi Marc,
> 1) Working, separately editable/instanceable/properly previewable > clusters (I know, I know, it's complicated and you're working on it!!) > 2) A Send/Receive data component ... I'm assuming > this is a fairly simple thing to implement? It would be a godsend. It would be fairly simple to implement. And I can see the huge organisational benefits. Maybe I can slip one of these in before the next version is released. But since I kinda-sorta promised Bob it would be next week, I'm not sure if I can make that. > 3) Previewed geometry "always on top." ... Is there an easy fix to make > the current preview component ALWAYS show in green over the top of all > red previews? I don't know. I'll have to discuss this with our main OpenGL guy, and then hope that it's possible in DotNET as well. It would incidentally be fairly easy to add Stored Preview States to Grasshopper. Does that sound like something you might still use if the other option would also be available? > 4) Gates and switches. Again, I use Max/MSP as a model... but having > controllable gates allows you to set up testing scenarios and quickly > switch between states. Also has implications for conditional data > manipulation. There are some gates and merge components available now, but we need a lot more. Feel free to post some detailed descriptions of the functionality you're looking for. > 5) Undo. If only to save myself from those moments when the mouse > slips and I connect to the wrong input, therefore initiating the "What > was this connected to?" adventure. Undo is about half finished (has been for months, haven't had the courage to tackle the second half). It should be available sometime soon. But not very soon. -- David Rutten [email protected] Robert McNeel & Associates
