Maybe it's just a silly thought, but wouldn't the whole wireless connection concept be more intuitive and useful if there were additional "transmitter" components?
I imagine it could work like this:
1. Somewhere on the canvas you insert a Transmitter component, set the number of input parameters and connect data. Somewhere else you create another component for a different data set.
2. In a distant part of the GH universe, far far away, you insert a Receiver component, right-click and choose the outputs you want - from a list of currently transmitting "data channels" in the definition. You could also make the connections the usual way by dragging wires from the transmitters.
I think that it would help organize large and complex definitions and make them more legible with the use of a reasonable number of Transmitter/Receiver components.
I actually think that Luis is on a good track with just being able to make all nodes available to transmit/receive. Then we don't have to worry about having special components to do so.
Extending this thinking to how transmitters fit into workflows, I've been thinking that the ability to select wires would be extremely beneficial for a number of reasons. In this case, it would be nice to be able to just select a wire, right click on it, and say "Switch to Transmitter" or something to that effect.
Actually, I've learned to loathe the Receiver component. It's completely messing up my ability to read other people's networks. This UI needs some serious attention and probably some global overrides.
Luis' suggestion makes the most sense to me, why introduce more types of object if this could be done by adding an option to the existing objects?
WT4
Sep 22, 2009
Damien Alomar
Extending this thinking to how transmitters fit into workflows, I've been thinking that the ability to select wires would be extremely beneficial for a number of reasons. In this case, it would be nice to be able to just select a wire, right click on it, and say "Switch to Transmitter" or something to that effect.
Sep 22, 2009
David Rutten
Actually, I've learned to loathe the Receiver component. It's completely messing up my ability to read other people's networks. This UI needs some serious attention and probably some global overrides.
Luis' suggestion makes the most sense to me, why introduce more types of object if this could be done by adding an option to the existing objects?
Sep 22, 2009