See: Description
| Interface | Description |
|---|---|
| AppEventSupport |
This interface is a marker for all objects that want to
form a "chain of responsabilty" to dispatch events to
receivers.
|
| Class | Description |
|---|---|
| AppEvent |
AppEvent is the base class of all events that use the AppEvent
mechanism.
|
| AppEventManager |
A AppEventManager object can be used to dispatch events to registered listeners.
|
| AppEventUtil |
Small helper class to make implementing AppEventSupport more easy:
the default case is to forward the event to an objects "parent".
|
| BindEvent |
A BindEvent object is used to bind AppEvent classes to (any number of)
event receivers.
|
| UnbindEvent |
A UnbindEvent can be used to remove the binding that was
established with a BindEvent.
|
The AppEvent library provides the anonym sending and receiving of events.
The event sender doesn't know the receiver of a event, and vice versa.
The only shared knowledge between sender and receiver are the type
(class) of the event.
The process of binding the receiver to a sender also works via the AppEvent concept:
With posting a
object the receiver (an object of any class) can bind one of its methods
to an BindEvent type.AppEvent
There can be any number of receivers for a given event class, the all
get notified in a undefined (but deterministic) order.
In most GUI applications, certain parts (e.g. the various dialogs) are
connected in some hierarchical way. When this parts implement the
interface,
their relation can serve as an "chain of responsibility" for the
AppEvent's.AppEventSupport
At the end of such a chain is typically a object, that does the
dispatching of all events that were not consumed on the way through
the chain.
AppEventManager
Copyright © 2017 Jürgen Zeller (privat). All rights reserved.