@parabola s/r nodes introduce a framedalay, just like pads. they are written to in one frame and read out the next frame. in many cases thats not desirable.
The inspiration comes from Variable Receiver and Variable Broadcaster nodes present in Origami, a UI prototyping tool made for designers. Here it is in action.
Few notes:
Like pads can be mass renamed from Properties panel, the panel should also include option to mass rename these broadcast/receiver nodes as well
Like pads, these will have patch level and region level scoping
The context menu for receiver nodes should include an option “Jump to broadcast node”
A receiver node of the same name should not be allowed to link to its broadcast. This will eliminate the question “How will these behave in a loop?” and the answer would be that each iteration would get a fresh pair of broadcast node and receiver nodes.
This will also make Send (Local) and Receive (Local) nodes redundant which is great, as their use-case was limited anyway