In my application, I have different classes for UI components and for their event management.
While my initial thought is to have separate classes for Window and Frames and then a Window would have composition of Frames.
And there should be a single entry for creation and delegation of the events happening either at Window or Frame/Control level.
However, I’m unable to conclude on a pattern of this sort.
So, currently ending up with separate event handlers which are directly linked to their respective UI frames/controls.
Please guide my in selecting a good pattern for this use case.
EventAggregator pattern should be your way to go. It totally decouples your modules from each other. By this way, modules don’t need to know(or reference) of the other one.
You can see my another (more detailed) answer about the same topic here.
If you don’t need that much loose coupling (e.g. modules have the reference to each other), you should take a look at Observer pattern. It is another method to implement distributed event handling mechanisms.