Hey All,<br><br>I&#39;m looking to improve a program&#39;s design with regards to how it communicates between the &quot;jack&quot; thread and its &quot;main/gui&quot; thread. Please note I&#39;m *not* looking for implementation details like what ringbuffer to use, this has been discussed here before.<br>
<br>Conditions:<br>Gui needs to feed data trough to the jack thread (data = parameter moves etc)<br>
Jack thread needs to push data (buffers for waveforms &amp; &quot;playhead&quot; info)<br><br>The real question:<br>What is a neat solution to passing various data trough a ringbuffer?<br><br>My (hacky?) solution: Create a class, call it &quot;Event&quot;. Runtime now looks like so:<br>
1. Create a EventType enum, set the details<br>2. Write those &quot;Events&quot; into the ringbuffer<br>3. Switch based on EventType, and handle the event.<br><br>While not terribly ugly, that Event class starts to get bigger &amp; nastier, so I concidered sub-classing it... but I&#39;m not sure this is going in the right direction.<br>
<br>I&#39;m very intrested how the &quot;big&quot; programs around have approached this problem... Cheers, -Harry<br>