Hi Frane, I'm running late, I'll have to be brief:
1. Data always flows from outputs to inputs. You cannot reverse components so data can only ever flow in a single direction. 2. I'm planning this, but not any time soon. At the moment the connection are just pointers from one parameter to another. I need to rewrite this entire segment of the core so that wires can have properties. 3. With grid alignment, what parts of the components should snap to it? The centre? The upper left corner? All corners? 4. How do I know which new parameters are supposed to replace which old parameters? Most components have different inputs/outputs, so it's not obvious which connection make sense if you switch out a component. 5. I can make this work for parameters, probably. But not components. How would I know which input parameter is supposed to grab the connection? 6. I'm planning to expose more objects on the Remote Panel. At any rate, the Remote Panel is overdue for a massive face-lift. 7. This is way too difficult :) No way am I even going to think about that! 8. ..see (1) 9. This is something I'll be looking into once connections can have custom settings. Or do you want a global switch? 10. (& 11 & 12 & 13) The next big project on the list is to rewrite Clusters from the ground up. We want clusters to behave like fun-sized networks. Pretty much like what you've described. ----------------------------- 1. You can use a Merge Multiple Component to orderly connect input streams. It has variable inputs so you can always add more. Another feature I'm planning is to draw little text tags over wires, that indicate in which order they are joined. 2. It's probably not that difficult to disable specific output parameters (for example, you could disable Origin, X and Y in [DecomposePlane], leaving only Z), but actually changing the type of outputs is very complicated and also puts a huge amount of responsibility on Component Developers. I'm trying to keep the Component SDK as simple as possible (not sure if I'm succeeding). 3. Agreed. There's very little I can do about this, maybe Rhino5 or the RDK will offer some solutions in the future. Basically, I'd have to bake the geometry anyway or else the Render engine won't know it exists. If I start to bake stuff all the time, there's be a huge overhead slowing everything down and absolutely hogging the Rhino undo- system. -- David Rutten da...@mcneel.com Robert McNeel & Associates
