Hi All,<br /><br />Recent thoughts of mine include changing the &quot;direction&quot; of operations in real-time program design:<br />Eg: Don&#39;t call a set() on a Filter class to tell it its cutoff, every time there&#39;s a change,<br />but make it ask a State class what its cutoff should be every time it runs.<br /><br />I&#39;m now considering implementing this pattern, but I&#39;m wondering have others done this before?<br /><br />Along the same lines, say I have a single linked list of AudioElements, and the 3rd element needs info, should<br />it request it, be told it, or have some other system to inform it of events?<br /><br />I&#39;m seeing downsides to each approach:<br />1: Tell it on every change -&gt; performance hit<br />2: Request it every time it runs -&gt; Keeping control over the many values & unique ID&#39;s of class instances<br /><br />Experience & Opinions all welcomed, -Harry