hi there dear list people, a little while ago, andy mentioned a construction for bypassing gui objects (numberboxes, in that case) while at the same time using the info you may put in them with the mouse. i can't find the post anymore, but i think that's exactly what i need now. i'm making an abstraction for my midi controller (drum pad thingy), that should both show what comes in--ie bang the nicely coloured [bang]s when the pad with the corresponding notenumber is hit--and function as an onscreen replacement: when a [bang] is clicked, it should send it out. in other words, i'm looking for a way to have incoming info stop at the [bang] (as it'll come out directly), but info generated at the [bang] move on. hope i make myself clear... anyone have any idea? thanks a lot! cheers, robbert
robbert van hulzen wrote:
in other words, i'm looking for a way to have incoming info stop at the [bang] (as it'll come out directly), but info generated at the [bang] move on.
Well, you can't stop info at a bang, but you can stop the output with [spigot], as in the ascii below:
in | [t b a b] | | | | gui | | | | "1" / "0" \ / | X | / \ | / \ | | \ | | \ | [spigot 1] | out
(the creation argument to spigot is the initial gate state, at least in recent Pd versions)
Thanks,
Claude
i don't think this is possible.
a workaround would be to change the color of the bang for 250 ms so
the whole thing is black if a hit gets detected.
[color 22 0 0( | [t a b] | | | [delay 250] | | | [color 0 22 0( | / | / [bng]
Am 31.10.2007 um 15:10 schrieb robbert van hulzen:
hi there dear list people, a little while ago, andy mentioned a construction for bypassing gui
objects (numberboxes, in that case) while at the same time using the info
you may put in them with the mouse. i can't find the post anymore, but i think that's exactly what i need now. i'm making an abstraction for my midi controller (drum pad thingy),
that should both show what comes in--ie bang the nicely coloured [bang]s
when the pad with the corresponding notenumber is hit--and function as an
onscreen replacement: when a [bang] is clicked, it should send it out. in other words, i'm looking for a way to have incoming info stop at the
[bang] (as it'll come out directly), but info generated at the [bang] move on.
hope i make myself clear... anyone have any idea? thanks a lot! cheers, robbert
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
-
Claude Heiland-Allen -
Max Neupert -
robbert van hulzen