Hi Sara,
#1. When you specify a gemhead render priority then the gemchains with the smallest priorities get rendered first. [gemhead 1] first [gemhead 5] second.
#2. If you have a bunch of gemheads without render priorities [gemhead] they are rendered in an "undefined" order. Really they are rendered in the order you create them, the first gemhead you create gets rendered first and so on. To make them undefined you use the render order (#1)
#3. separator is a lot like a gemhead, separators don't allow you to specify the render order, so the render order is the order in which you create the separator objects like #1.
#4. To control the render order of separator's you use [t a a a a] to set which separator from a particular gemhead gets rendered first.
I think that covers it.
.b.
sara kolster wrote:
Hey,
I didn't think it was a Gem problem, but I was facing the problem when I was working on a patch and the last 'modified' separator would always show on top. But, as I understand you suggest that I could use [t a a] which should provide this from happening. Right?
Sara
the problem you are experiencing are pd-problems and not really Gem-problems: controlling the execution order!
just use the tools provided by pd for manipulating the data-flow. with things like [spigot] and [t a a] (before the [separator]) you can do astonishing things.
note that there is one thing you should _not_ try: using delay-lines for the messages passed between Gem-objects!
mfg.asdr. IOhannes
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list