Event Dispatchers would work best here:
- let’s say this is the slot, calling a dispatcher when its border is clicked:
- and this is the Load Game that adds those slots, we bind a delegate to the dispatcher’s call:
Above, clicking any the dynamically created widget would remove it.
How to make children widgets interact with parent?
What I posted is an answer to the topic.
ideally clicking a slot would only “select” it and then clicking the “load” button below would load it, and then I’d be able to add a “delete” button next to it.
Not sure what this has to do with the parent vs child interaction, though. Sounds like this could be handled by the slot internally. The scrollbox in the parent does not need to know what the children are up to. But…
If you want to handle the Select/Load/Delete in the scrollbox widget that houses the slots (sounds like a valid idea as it would then act as a manager and/or keep track of things) I’d do it with the dispatchers.