So that you don't have to insert a <> component every time you want to do something when a widget is pressed.
You can have a default one, present in the component's panel, and on the executing phase, it will have priority ONLY if there is not already an explicit <> script (ClickTriggered) linked to that component. And if this is the case, the return screen-id should also work. This would greatly simplify dynamic transitions and prototype-app-state modifications on any component press and will free up the canvas on having to many confusing <> script components.
So that you don't have to insert a <> component every time you want to do something when a widget is pressed. You can have a default one, present in the component's panel, and on the executing phase, it will have priority ONLY if there is not already an explicit <> script (ClickTriggered) linked to that component. And if this is the case, the return screen-id should also work. This would greatly simplify dynamic transitions and prototype-app-state modifications on any component press and will free up the canvas on having to many confusing <> script components.