How are states set for each pass though the user code loop?
From Bill Sobel on 02/2003: Misterhouse works on a multipass system where a state becomes ‘new’ for one (and only) one pass thru the system. The actually timing of the passes varies (based on the machine, the load, the code, etc) but you generally can presume multiple passes will occur per second (I’m getting about 19 per second with fairly light load on a 400mhz laptop). I ran into an early problem where MH didn’t handle multiple states being set during one pass (each subsequent state would ‘overwrite’ the previous one). As an example if my object read from a device and noticed that both the volume and treble setting on my mixer changed, it would generate a volume state and a treble state. The treble state when overwrite the volume state. To fix this Bruce introduced a queue of states. So, when a module sets a state, it gets set for the ‘next’ *available* pass thru the system. In the example above (presuming no other states are outstanding) the volume state would be ‘new’ during curre
