I am desperately looking for a way to trigger a button that is coded into a component. You can see it here in Instance Manager (V126.96.36.199) in the Insert Block component.
For some reason it used to be a trigger input (on the broken old version), but now is a button on the component itself and doesn’t have a trigger input any longer.
Maybe @andheum knows a way to do this with something Metahopper-like!? The problem is that I have multiple of those components in the depth of a large definition and just need to trigger them using a button (and RCP).
I don’t know why you would create such components that for some reason include UI elements? It makes no sense at all to have a UI button included in the component and I think frankly they should not even be allowed. It saves you creating one button, but you lose so many possibilities of triggering a certain component. It’s enough that there are tons of right-click options on some components, but usually you set those once. Triggering a function however should never involve first finding the component in a large definition and having to click the button for each one separately.
@DavidRutten is it possible to have some stricter rules for GH2 please. Attributes and options should all be exposed as pins for true parametric coding. What’s your take on those buttons?