Hi Frank, hi guys,<br><br>Many, many thanks for your explanation and your example ! I've finally understood how to use [trigger] objects and store value in a [float] (I have to admit I needed quite a lot of time, a paper and a pen: I must be very slow "thinking in Pd" :)). Indeed, a nice exercise.<br>
<br>I have one question though (not related to [trigger]). In your example, as in Martin's, you use $0-a16 to name the array. I understand $0 is used when building an abstraction and creating multiple instances of this abstraction. My question is how can I configure this array, from the parent (from the patch using the abstraction) ? For instance, I'd like to add "xticks", "ylabel", etc... I usually use a message, like:<br>
_________________<br>[array1 ylabel -1 0 1 (<br><br>but the same with $0-a16 obsviously doesn't work, since $0 is not known (I understand it's a counter incremented at each creation). Is this possible to do this ?<br>
<br><br>Cheers,<br>Seb<br><br><div class="gmail_quote"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Hallo,<br>
Sebastien Lelong hat gesagt: // Sebastien Lelong wrote:<br>
<br>
</div><div class="Ih2E3d">> Thanks for your help. I'm getting things that "kind of" scroll... building<br>
> an horrible patch :) Some values are random, I guess I have a problem when<br>
> access extremities of the array. I'm sure there's something simpler,<br>
> probably using trigger, but I can't figure out how I could use a trigger<br>
> here. Could you give one last hint ? I guess I need to learn how to "think"<br>
> pure data...<br>
<br>
</div>Indeed: Understanding triggering and execution order brings you much<br>
closer to "thinking in Pd". There are only two things to remember: The<br>
left inlet of (most) objects is hot, the right is cold and lets you<br>
use an object as a storage container.<br>
<br>
OTOH the right outlet of (most) objects fires before the left one.<br>
This holds especially true for the [trigger] object whose main purpose<br>
is to control the order in that your patch cords get activated.<br>
<br>
Both facts are nicely combined in the scrolling table solution in the<br>
attached patch. The top [trigger] object shows how sometimes in Pd you<br>
have to think far ahead: Its right outlet stores a number in a float<br>
object below that gets used much later.<br>
<br>
The lower trigger object (abbreviated as [t ...]) shows another common<br>
idiom: It's followed by crossed patch cords. You will often see this<br>
when something is stored for a moment and the previously stored value<br>
is used instead.<br>
<br>
Anyway the attachement shouldn't be to hard to folllow with its<br>
comments, but feel free to ask any questions. "Getting it" is<br>
important here. :)<br>
<br>
Ciao<br>
<font color="#888888">--<br>
Frank Barknecht Do You RjDj.me? _ ______footils.org__<br>
</font><br>_______________________________________________<br>
<a href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>
UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Sébastien Lelong<br><a href="http://www.sirloon.net">http://www.sirloon.net</a><br><a href="http://sirbot.org">http://sirbot.org</a><br>