Events

class mundo.api.events.Event(
value
)

The different types of application events.

An event allows separate modules of the code to hook into the application at certain points in time and run custom code.

The value of each event should be the same as a method in the BasePlugin class.

For example, if the user wants to send a signal to an external measuring instrument before the sampling process is started, this can be done by hooking into (subscribing) to the ON_START event. Similiarly, if you want to stop the measurement once the sampling process stops, you can hook into the ON_START event.

Events are broadcasted to application plugins using the broadcast() method.

ON_SESSION_LOAD = 'on_session_load'

ON_PLATFORM_LOAD = 'on_platform_load'

ON_SESSION_SAVE = 'on_session_save'

ON_PLATFORM_SAVE = 'on_platform_save'

ON_SYSTEM_SAVE = 'on_system_save'

ON_CONNECTED = 'on_connected'

ON_DISCONNECTED = 'on_disconnected'

ON_READY = 'on_ready'

ON_START = 'on_start'

ON_STOP = 'on_stop'

ON_RESET = 'on_reset'

ON_DESTROY = 'on_destroy'

ON_SAMPLE_SELECTED = 'on_sample_selected'

ON_SAMPLES_UPDATED = 'on_samples_updated'

ON_QUEUE_UPDATED = 'on_queue_updated'

ON_MODE_UPDATED = 'on_mode_updated'

ON_PROCESSING_SAMPLE_UPDATED = 'on_processing_sample_updated'