sub_arctic.input
Interface dispatch_handler
- All Known Implementing Classes:
- debug_lens_top_level
- public abstract interface dispatch_handler
This class has been provided an extensibility hook for the particular
purpose of allowing code that monitors the effects of input dispatches
of other people's code. When an object implements this interface
and then sets itself to the current event dispatcher handler in the
manager it will be notified after each successfully dispatched
input event is processed.
Note that this is quite different than the active role that an agent
could play in the event dispatch process. If you put an agent in the
monitor focus policy, it could filter and/or become aware of every
event before they are dispatched by the other agents. Using the
monitor focus policy is the correct way to implement some type of
active global policy on input handling. This interface is provided
for a more passive approach.
In particular, this interface is primarily targeted at people who have
some type of input logging procedure that they wish to accomplish. An
example might be for usability experiments, in these cases it is good to
have complete record of what happened with the interface. Any existing
interface (even with code you didn't write) could be easily modified
to allow complete logging using this interface and the manager.
Method Summary |
void |
handle(dispatch_result dr)
This method is called by the manager if the dispatch_handler is the
system's current event_dispatch_handler. |
handle
public void handle(dispatch_result dr)
- This method is called by the manager if the dispatch_handler is the
system's current event_dispatch_handler. The manager will call this
method each time an event is successfully dispatched.
- Parameters:
dispatch_result
- dr the result of the dispatch from the agent