stephen,
i've been working on a patch that divides my Kaos pad into sectors for
this express purpose. the basic scheme is:
[ctlin]------[>36]-------[<38]-------[select 1]----[bang]------[toggle]
with a [metro 100] sending "0" to the [>n] to reset it. use the logic
output of the [<n] object to trigger the [select 1]. the constant stream
of zeros will reset the whole patch correctly, as long as you dont need
to touch your button twice in 100 ms.... then every time it gets your
value, say "37" in this case, it will "bang" the toggle.
the Kaos pad patch does this for 30 different toggle boxes, depending on
where i touch the pad, so the number filtering is more complex [and
isn't quite finished yet :-) ]. but this is a good place to start. mail
me offlist if you don't quite grok this and want to see my spaghetti...
derek
Quoting Stephen Martin <squaw(a)lollygagger.org>:
>
> I can get input from the buttons, but (like matthew said) it's not a
toggle,
> so I can only get a positive value for as long as my finger is on the
> button. It goes back to zero when I lift my finger off.
>
> so, here's what I think would work, but I don't know PD well enough to do
> it... and this is where I need the quick help... it seems simple in
> theory...
>
> is there a way to have a toggle triggered with, say, a value of 37,
but not
> go off when it receives a value of 0... and THEN, go off when it receives
> the 37 value again - basically every time this value is passed, the
toggle
> goes off or on, but by only using one value, not a zero and a positive
> integer...
>
> help?
>
> STEVE