Introduce the event dispatch abstraction about vulkan-performance-layers HOT 2 CLOSED

In the initial design of the EventLogger, I didn't know that each layer has its own instance of LayerData. I assumed that the LayerData is a shared object among all the layers and should contain all the Loggers. In that scenario, we needed a mechanism in the LayerData to forward the incoming events to their corresponding loggers. I thought using a key-value map (Dispatcher) seemed like a good idea.
However, since each layer has its own instance of LayerData, it can have its logger in its LayerData. The Events created by a layer will be passed to the layer's logger residing in its LayerData. Hence, there is no need for keeping track of the origins/destinations of the events and the Dispatcher.
This is why I closed this issue.

from vulkan-performance-layers.

Thanks for taking care of the issues! @miladHakimi can you add a comment to briefly explain why this is not longer needed?

from vulkan-performance-layers.