Abstract out sending of events

This removes the details of how events are handled from drivers, so the owner
can set them up to do anything.  For example, a driver could be run in the GUI
thread and have its events simply dispatched immediately, but here everything
is enqueued to the same queue which is drained later for simplicity.

1 files changed, 1 insertions, 8 deletions

diff --git a/src/JackDriver.hpp b/src/JackDriver.hpp
index 1e680a0..6c9c05e 100644
--- a/src/JackDriver.hpp
+++ b/src/JackDriver.hpp
@@ -19,24 +19,21 @@
 
 #include "ClientInfo.hpp"
 #include "Driver.hpp"
-#include "PatchageEvent.hpp"
 #include "PortInfo.hpp"
 
 #include <glibmm/thread.h>
 #include <jack/jack.h>
 
 #include <mutex>
-#include <queue>
 #include <string>
 
 class ILog;
-class Patchage;
 
 /// Driver for JACK audio and midi ports
 class JackDriver : public Driver
 {
 public:
-	explicit JackDriver(ILog& log);
+	explicit JackDriver(ILog& log, EventSink emit_event);
 
 	JackDriver(const JackDriver&) = delete;
 	JackDriver& operator=(const JackDriver&) = delete;
@@ -73,8 +70,6 @@ public:
 	jack_nframes_t buffer_size();
 	bool           set_buffer_size(jack_nframes_t size);
 
-	void process_events(Patchage* app) override;
-
 private:
 	ClientInfo get_client_info(const char* name);
 	PortInfo   get_port_info(const jack_port_t* port);
@@ -101,8 +96,6 @@ private:
 	ILog&          _log;
 	jack_client_t* _client;
 
-	std::queue<PatchageEvent> _events;
-
 	std::mutex _shutdown_mutex;
 
 	jack_position_t _last_pos;