I am using [counter] in updown mode counting from 0 to 10. I send the message "set 1," then start sending bangs.

Expected behavior: counter outputs 1 2 3... 9 10 9 8...

Actual behavior: counter outputs 1 0 1 2 3...

Why is it counting down rather than up and what is a simple way to remedy this?

I am using [counter] in updown mode counting from 0 to 10.  I send the message "set 1," then start sending bangs.  

Expected behavior: counter outputs 1 2 3... 9 10 9 8...
Actual behavior: counter outputs 1 0 1 2 3... 

why-is-counter-doing-this

> It's quite logical, because it's going down.

But this is the first message/bang counter receives. Updown mode begins counting upward; I don't see why this should be any different.

> It's quite logical, because it's going down. 

But this is the first message/bang counter receives.  Updown mode begins counting upward; I don't see why this should be any different.


> Expected behavior: counter outputs 1 2 3... 9 10 9 8...

> Actual behavior: counter outputs 1 0 1 2 3...

i don't understand what do you want for behavior.

0 1 2 3 4 5 6 7 8 9 10 9 8 7 6 5 4 3 2 1 0

> Expected behavior: counter outputs 1 2 3... 9 10 9 8...
> Actual behavior: counter outputs 1 0 1 2 3...

i don't understand what do you want for behavior.
in updown mode the counter will print : 

or u might be able to roll your own modified counter using the [accum] object.

but i do not know why do you not need zero at start ? 

anyway this is a demo of what [js] can do...

but i do not know why do you not need zero at start ? 
anyway this is a demo of what [js] can do... 

Why not just send it the message "set 0, set 1". That seems to set it in the upward direction. No need to use two counters.

why is counter doing this?