Alright, so I've traced this a few times, R'd TFM, and searched the forums and could use a few fresh sets of eyes on the problem. The attached patch is a generic example of a problem I've been having when trying to use zl queue in an iterated loop. The process is as follows:
1. Loadbang bangs uzi, which counts to 6 out its right outlet, giving us integers 1-6 in the queue.
2. Bangs from the button SHOULD cause zl queue to output the oldest item in queue (left) and the number of items remaining (right).
3. These outputs are packed and printed.
4. The list is then unpacked and the number of remaining items in queue (from the right out of zl queue) goes to sel 0, with a bang going to the uzi at the top of the patch when the input to sel matches 0.
The idea is that the queue (zl queue) gets refilled (uzi) as soon as it's empty (sel 0), so continuing to click the button SHOULD produce an output (print) of:
...ad infinitum. INSTEAD, it seems that on the second time through the cycle, the first value to leave zl queue is 2 and not 1. Tracing reveals nothing useful so far as I can tell; the 1 from uzi goes into zl queue and is reflected in the count, but cannot be banged out. What we actually get in the Max window is:
...and then nothing, of course, as the count never hits 0, so sel 0 can't bang uzi again. So, is this a legitimate bug, or am I missing something here?