William Echard

I'm hoping someone can sort me out on a detail of counter resets. I've noticed that regardless of whether you reset to minimum using the "immediate" change inlet or "next clock" inlet, the state of x_curcount always goes to the minimum right away -- it doesn't wait until the next clock count in either case. Is that the way it's supposed to work, or am I missing something? I've attached a patcher that demonstrates what I'm asking about if that makes the question more clear. Thanks...

P.S. This is also my first attempt at including a patcher in a forum posting, so if it didn't work then I could also use some help on how to do that!

question-about-counter-and-x_curcount

OK, so now I see that the difference between the two is the state of the startup flag. So my question has changed a bit -- is there a message that can be sent to set that flag directly and leave everything else the same? My interest in this is academic right now, but I'd like to be able to keep playing around and seeing how the counter responds in various situations, and directly setting the startup flag could be useful for that. Thanks...

Question about counter and x_curcount