alberto-bernal

I was two hours dealing with the following patch -also in trace mode- and I didn't catch my error. Am I forgetting something or could it be that there is a bug in the counter object or some of the other objects I use in the patch. The patch is a part of a bigger one that should perform an automatic counting action for dumping matrixes. 

Hello,
  I was two hours dealing with the following patch -also in trace mode- and I didn't catch my error. Am I forgetting something or could it be that there is a bug in the counter object or some of the other objects I use in the patch. The patch is a part of a bigger one that should perform an automatic counting action for dumping matrixes. 
  Thank you for your help,

bug-in-counter-or-im-just-blind

I don't really understand why your patch gives a stack overflow but it looks like it's working if you trigger 0 "on next clock" instead of "immediately" and then send a bang to start counter...

BTW did you think about using [uzi] instead of [counter] ?

I don't really understand why your patch gives a stack overflow but it looks like it's working if you trigger 0 "on next clock" instead  of "immediately" and then send a bang to start counter...
BTW did you think about using [uzi] instead of [counter] ?
Hope that helps.

Thank you very much for the work-around, now it works. I cannot use uzi, because I need to send the numbers "manually", in order to trigger other actions for every one of them. 

Thank you very much for the work-around, now it works. I cannot use uzi, because I need to send the numbers "manually", in order to trigger other actions for every one of them. 
  Cheers,

bug in counter or I'm just blind...