Well, wxWidgets does things unusually. You can say that an event is like this, but in other, better, systems there is a single event, and then that event is forwarded up the hierarchy, by way of new events. So I suppose, yes, the terminology can be construed more than one way. But what I meant, is with Bind and Connect, the context you set up for processing the event object, I call an event. That's the context I mean, clearly. Without wanting to play word games.ONEEYEMAN wrote: ↑Thu Sep 05, 2019 6:18 pmHi,
But what problem you are trying to solve?
And just to add to the discussion - not all events can be handled.
Or some events can have multiple event handlers.
Or some events can be handled both in parent and the child classes.
How do you handle all possible scenarios?
If events are not realized in the absence of a handler, then retrieving the handler (as if user data) is something that would be useful, and it's exactly what is done when you give it a "this" pointer in most instances, although that is technically separate, since it doesn't have to be the address of the event handler that is the object of the Bind or Connect call.
I don't know the details, so I ask. There's certainly no meaningful overhead in exposing that pointer. It would be a useful pointer to have in any event.