restore states across nodes

Replies to This Discussion

Permalink Reply by Danny Boyes on April 16, 2014 at 8:56am

Not directly. EDIT: I should say with native grasshopper methods. You can probably do it by a Script

You can put a [Graph Mapper] inside a cluster and copy the cluster around the canvas, updating one will update all. But this does mean that you will not be able to see the results as you alter the graph

Permalink Reply by Danny Boyes on April 16, 2014 at 9:05am

Thinking on about this I cannot see a benefit to having to pass different data through different but the same Graphs. If you manage your data trees or the results from your graph better you should be able to use the same one. Can you post a file to demonstrate you issue?

Permalink Reply by Danny Boyes on April 16, 2014 at 9:20am

Here's an example where I have got 4 different sets of values to map based on a generated set of values for a graph.

Permalink Reply by dk2079 on April 16, 2014 at 9:37am

Hi Danny,

thanks for sharing your thoughts. in deed it would be possible to process and recover several input lists at once , but the situation is more like that i copy a setup to create another "deformation" in a surface. or two or three..

I want individual control of each, but would like to have a bunch of "presets" as starting point.

Permalink Reply by Danny Boyes on April 16, 2014 at 9:55am

Ok it's a bit like the [Gradient] component then, which does have this feature where by you can save a setup and recall it from any [Gradient].

Personally I think there should be another method where you can "tether" a [Graph Mapper] or [Gradient] component to any other one and receive its input. Similar to the Hookup of the [Timer] to components. I made this wish about 3 years ago but to no avail.

Permalink Reply by dk2079 on April 16, 2014 at 10:08am

yeah, i had a similar thought the other day.

like a wireless transmitter. i remember there used to be a sender/reciever some time ago.(before i really got into it)
i mean it working like:

you have 1.) a transmitter, you can activate it on any output. and it has a channel you set.1,2,3,4...

you have 2.) a receiver. you can tell it to which channels you want to listen, and you can define their order.

Permalink Reply by Danny Boyes on April 16, 2014 at 10:16am

Wire Types replaced the [Receiver] and I know David is working on a method for GH2.0 where by you can use Globally Named Parameters but the thing that is needed to be receive is the USER input i.e. the grips that you move around. This isn't available from any output.