Signal / Wait for Signal Suggestion

I'm working with Construct several years and i'm not happy with the use of "signal / wait for signal" actions because not make me sense was "wait for signal" being an action.

My suggestion it's about to change "wait for signal" from being an action to an event so that way make sense with the "event/action" pattern that currently used in this game engine.

I attach an image to show in summary an example of my suggestion:

Wait for signal, and signal is best in places where you want to wait x amount of time within the same condition, sub conditions, or related conditions. Like when you need a tick for something to complete. User interaction, gpu action, etc.

If the "signal" action runs a "wait for signal" event, isn't that the same as just calling a function?