Is there a way to echo the balloon information and/or the warning/error color of a component from inside a cluster to the outside of it so it would be directly visible from the Grasshopper document without editing the cluster?
in my example the cluster contains the purple group with access to all the other inputs and outputs. I’m wondering if there is a way to make the cluster itself turn orange with the warning and echo the balloon from the script to a balloon on the cluster itself?
Cluster.gh (40.2 KB)
Hello,
I don’t think there is a native solution, and I’ve found old threads requesting this feature with no reply.
So… Here is a workaround, using Metahopper to gather all clusters of the document, and a custom C# component to loop through all components inside each cluster, collect the error messages and apply them to the cluster !
You’ll need to download Metahopper from Package Manager.
ClusterErrorMessages.gh (13.2 KB)
2 Likes
@magicteddy Thank you again for your help. That could not have been easier to get working! Metahopper was detected in the document and was downloaded automatically.
There is actually a problem, the Metahopper component does not react to all events, especially wire changes or slider modifications, but only to added/removed components. Which means that the C# script has to be recomputed manually for the messages to update.
As a workaround, you can add an input to this component and link any output of all your clusters there. This will force the update anytime a cluster is recomputed.
1 Like
Thank you for finding this and providing a workaround. I saw what you meant by it not re-evaluating, but making the connections to my clusters does solve the issue. I named my input Evaluate to remind me why I have all those wires connected there.
Connecting them all to a relay contact like this doesn’t seem to cause a problem, I just wanted to control the wires some, is there any reason not to connect them like this? I probably don’t need to connect it to all of them, because changing anything would make them all re-calculate anyway.
Cluster Warnings and Errors.gh (6.1 KB)
You could hide those wires.
As a good practice, I always advise not to merge wires like this, but to use Merge component - which also acts as a relay of sorts. But for this particular case, it’s fine.
1 Like
I never noticed that, Thanks for the suggestion!
It looks like you can only assign the wire display to inputs, is that correct? My clusters don’t seem to have that option on their inputs.
I would really like to hide the wires from this tolerance input that goes to all my clusters:
I set it to hidden but they didn’t hide, so just for fun I put a panel on the input and sure enough only the inputs were hidden.
I guess they had to pick one… either the inputs or the outputs control whether the wires are hidden or not otherwise it would be ambiguous what to do.
So I just put more primitives next to the clusters so I could hide the wires on their inputs:
Yes, hiding wire is only for inputs.
It should also be working for cluster inputs :
I don’t see the wire display option for my cluster inputs at all, if I click way over by the pin I get:
and if I click further over by the name of the pin, I get:
Maybe I did something wrong in my cluster?
Inside the cluster I have the wire display option on the C# script
Here is the cluster:
Non-Intersecting.gh (34.1 KB)
Yeah I don’t know what happened but it seems there is a problem with the cluster, I exploded it and recreated it and it works fine.
Non-Intersecting.gh (32.3 KB)
Knowing what it’s supposed to do is helpful 
Thank you for figuring it out.
