| Method summary | |
|---|---|
| run-tests | &optional package-name |
| Function summary | |
|---|---|
| deactivate-all-monitors | |
| print-all-events | |
| print-all-monitors | |
| Macro summary | |
|---|---|
| activate-monitor | id &optional (active t) |
| deactivate-monitor | id |
| define-event | id &body parameters |
| define-event-handler | (monitor-id event-id) &body body |
| define-monitor | id &rest init-arguments &key (class (quote (quote monitor))) documentation &allow-other-keys |
| notify | event-id &rest data |
| toggle-monitor | id |
| toggle-monitors | &rest ids |
| with-disabled-activation-of-monitors | &body body |
| with-disabled-monitor-notifications | &body body |
| with-disabled-monitors | &body body |
Prints all registered monitors. You can use this function to easily see which monitors are active.
Defines an event. This needs to be done before monitors using that event can be registered. 'parameters' is pairs of parameter names and their classes as used in method declarations.
| define-monitor | id &rest init-arguments &key (class (quote (quote monitor))) documentation &allow-other-keys | [Macro] |
Defines a monitor. Note that all monitors have to be defined before they can be used, e.g in defining event handlers. Parameter 'id' is used to identify the monitor. Documentation should contain a short string that helps other users to guess what the monitor does. If you want to use another base class than 'monitor', then pass this to 'class'. Note that you can pass arbitrary keyword arguments for the creation of the monitor.
Defines a handling method for an event a (list of) specific monitor. Pass the event id you want to handle to 'event'. The id of the monitor (or a list of many monitor ids) is passed to 'monitor-id'. The parameters for the method are automatically copied from the event definition of 'event'. The monitor instance is accessible with the parameter 'monitor'.
use this to run some code without monitor notifications
use this to run some code without monitor activations