That’s the best / cleanest way to communicate from child → parent, yes.
tl;dr:
Do note - if ALL you want is a simple click, native buttons already dispatch that, we just need to get to the button:
The above equals to: whenever a button inside the UserWidget is clicked, execute this Custom Event here. In this case you wouldn’t even need to create a separate event dispatcher.
Buttons (and other native widgets as well) come with built-in stuff:
So you can already execute their Events elsewhere. It does not even need to be the parent widget. You can have this custom execute in any another blueprint. We just need to connect it to the right place.
you wouldn’t even need to create a separate event dispatcher.
The real power of custom Event Dispatchers you add yourself (like in the previous post) comes from the fact that you can add data; as in:
Now your widget / actor can send this data when interacted with:
It’s by far one of the most efficient method to push a lot of data across in BPs.
Assuming you want to build a menu where every button does something different / unique:
An Event Dispatcher with an Enumerator could be perfect for handling all this. You’d get a single event in a single location where you decide what happens next.