Writing docs sure makes you question the simple things again! Like this:
Why is there both "graph" and "array" in the Put menu? Seems like the "graph" option is kind of a crippled "array" insofar as it doesn't actually even have a name to address it. At least *I* never use it when I need to put an array/table somewhere, but maybe somebody has a clever use for it. Is "graph" some sort of evolutionary holdover, or does it have a distinct purpose? Miller's manual doesn't go into details here.
best, d.
derek holzer wrote:
Writing docs sure makes you question the simple things again! Like this:
Why is there both "graph" and "array" in the Put menu? Seems like the "graph" option is kind of a crippled "array" insofar as it doesn't actually even have a name to address it. At least *I* never use it when I need to put an array/table somewhere, but maybe somebody has a clever use for it. Is "graph" some sort of evolutionary holdover, or does it have a distinct purpose? Miller's manual doesn't go into details here.
http://lists.puredata.info/pipermail/pd-list/2006-10/043013.html
in short: a graph is a graphical container that can hold several arrays. an array needs a graph to be displayed (read: whenever you create an array from the menu, you will be asked whether you want to put it into a newly created graph or into an existing graph; you cannot choose to not put it into any graph).
putting several arrays into one graph allows you to display data in an "aligned" way.
mfg.ards IOhannes
Perfect. This is the "plaintext" definition I was waiting for. I did read the thread in question already, but it wasn't so clear as how you just described it.
thx, d.
Ohannes m zmoelnig wrote:
derek holzer wrote:
Writing docs sure makes you question the simple things again! Like this:
Why is there both "graph" and "array" in the Put menu? Seems like the "graph" option is kind of a crippled "array" insofar as it doesn't actually even have a name to address it. At least *I* never use it when I need to put an array/table somewhere, but maybe somebody has a clever use for it. Is "graph" some sort of evolutionary holdover, or does it have a distinct purpose? Miller's manual doesn't go into details here.
http://lists.puredata.info/pipermail/pd-list/2006-10/043013.html
in short: a graph is a graphical container that can hold several arrays. an array needs a graph to be displayed (read: whenever you create an array from the menu, you will be asked whether you want to put it into a newly created graph or into an existing graph; you cannot choose to not put it into any graph).
putting several arrays into one graph allows you to display data in an "aligned" way.
mfg.ards IOhannes
Anyone want to add that to the FAQ?
.hc
On Dec 5, 2006, at 7:36 AM, derek holzer wrote:
Perfect. This is the "plaintext" definition I was waiting for. I
did read the thread in question already, but it wasn't so clear as
how you just described it.thx, d.
Ohannes m zmoelnig wrote:
derek holzer wrote:
Writing docs sure makes you question the simple things again!
Like this:Why is there both "graph" and "array" in the Put menu? Seems like
the "graph" option is kind of a crippled "array" insofar as it doesn't actually even have a name to address it. At least *I* never use
it when I need to put an array/table somewhere, but maybe somebody has a
clever use for it. Is "graph" some sort of evolutionary holdover, or
does it have a distinct purpose? Miller's manual doesn't go into details
here.http://lists.puredata.info/pipermail/pd-list/2006-10/043013.html in short: a graph is a graphical container that can hold several
arrays. an array needs a graph to be displayed (read: whenever you create an array from the menu, you will be asked whether you want to put it
into a newly created graph or into an existing graph; you cannot choose
to not put it into any graph). putting several arrays into one graph allows you to display data
in an "aligned" way. mfg.ards IOhannes-- derek holzer ::: http://www.umatic.nl ---Oblique Strategy # 152: "Tape your mouth"
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war
on terrorism. - retired U.S. Army general, William Odom
-
derek holzer -
Hans-Christoph Steiner -
IOhannes m zmoelnig