Hi, all-- this example from the MIT book is not working for some reason:

...the bang from the fourth output outlet of the select object is not banging the '0' message to reset the counter. I can manually click on the '0' message to reset the counter, but for some reason the bang is not triggering the message. Anybody know why?

Thanks!
Bryan

@bcgreen24 hi, i rebuild the patch and it is working for me...

@bcgreen24 You must have made the connection between [f 0] and [select] before the connection to [+ 1]. Without an explicit trigger, PD evaluates the connections for a given outlet in the order they were made. If you follow what happens when f is 3, it sets the cold inlet of f to 0, after which it increments 3 to 4 and overwrites the 0 that was just written with a 4. If you delete both connections from the f outlet and recreate them, first to the [+ 1], and then to the [select], it will behave as expected. But IMHO you should use a trigger, not only to enforce that order, but to make it clear that that order matters and is what you intended.

@jameslo you are right, i randomly connectet it in the right order

@Jona as would I, because we both think of that [f 0] [+ 1] idiom as a counter, i.e. a thing we'd complete before moving on to the next thing.

@jameslo Ohhhhh, I see! Thanks for that info, that's good to know.

Bryan

@bcgreen24 It is better to keep the counter separate: sequencer.pd

Otherwise use [trigger] to control the order of operation.