See Also: EventHandlerService Members
Developers may want to be able to write code in one place that handles events of a certain type.
Also, developers may need to globally change the behavior of the handlers for specific events or types of events, which may be distributed among designer components.
The designers for a typical project are many different objects so it can be useful to list and store reference to these events from a common place.
This service implements an "event stack" that contains the current set of event handlers. The stack may have a variety of different types of handlers on the stack.
For example, a designer might push, or add, a keyboard handler and a mouse handler onto the stack. When a designer requests an event handler, the service will find the topmost handler on the stack that matches the class you requested.
This way the service can be extended to any eventing scheme, and it also allows specific types of event handlers to be replaced. For example, you can replace mouse event handlers without affecting menu event handlers or keyboard event handlers.