Hi list!
I have made an abstraction for a table loop selection with data structure. That's the first I made with data structure, so I suposse there are some mistakes and some things I would like to improve:
I could't drag either the init point down to 0 or the end point up to 100.
one init marker and another end marker)
of $1_sample? (That's not necessarily but I'm cusious)
(via receive) I will be very thankful if someone can give me some advice in order to improve this abstraction. Thanks and regards.
Hallo, raul diaz hat gesagt: // raul diaz wrote:
I have made an abstraction for a table loop selection with data structure. That's the first I made with data structure, so I suposse there are some mistakes
There's a big mistake where you do the data subpatch traversal: There is no subpatch [pd 1_table] in your patch but still you try to do a [traverse pd-1_table(. Instead there is a [pd $1_table] subpatch. You should use something like
[symbol pd-$1_table] | [traverse $1(
instead, if you're using Pd 0.40, or
[symbol $1_table] | [makefilename pd-%s] | [traverse $1(
for older Pds.
and some things I would like to improve:
- I would like to limit init and end point rango between 0 and 100, that way
I could't drag either the init point down to 0 or the end point up to 100.
Check out the 09.scaling.pd help patch in the docs. You need to use a different syntax to paint, it looks something like this "x(0:100)(0:100)"
However for what you want to do, you need to change other parts of the patch as well and intruduce a "dummy-X"-coordinate. See attached patch.
- I don't know why I have two times the init and end markers (I only want
one init marker and another end marker)
Probably one was saved with the patch. If you clear the subpatch and put the markers on again, everything's fine.
- How can I modify either the init or end markers from an external value
(via receive)
You can send and receive pointers. Just get a pointer to one of the markers using for example traversal, then send that pointer somewhere, where you have a [set init x] object or so.
You can also store the received pointer in a [pointer] object, if you want to reuse it several times just like a [float] or [symbol].
Frank Barknecht _ ______footils.org_ __goto10.org__
Hi list, Hi Frank!
Thanks Steffen and Frank for your help!
I have remake my abstraction and I think now there is no mistake. Now I want to create my array "$1_sample" dynamically, but message "array" doesn't work. I receive "error: Bad arguments for message 'array' to object 'canvas'". Any suggestion?
Saludos.
Sorry...I forgot to attached my patch!
2007/2/3, raul diaz raul.lete@gmail.com:
Hi list, Hi Frank!
Thanks Steffen and Frank for your help!
I have remake my abstraction and I think now there is no mistake. Now I want to create my array "$1_sample" dynamically, but message "array" doesn't work. I receive "error: Bad arguments for message 'array' to object 'canvas'". Any suggestion?
Saludos.
Hi, did you try "table" instead of "array"? AFAIK, array is just the GUI-variant of "table"...
lg, Peter
raul diaz wrote:
Hi list, Hi Frank!
Thanks Steffen and Frank for your help!
I have remake my abstraction and I think now there is no mistake. Now I want to create my array "$1_sample" dynamically, but message "array" doesn't work. I receive "error: Bad arguments for message 'array' to object 'canvas'". Any suggestion?
Saludos.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
if the array is called 1_sample, then you just go:
[1 ( | [; $1_sample data data data(
you don't need any sort of "array" command or anything.
also, you can use a send box to send the data to your array, but remember that $1 has a different meaning in objects and messages.
[data data data ( | [s $1_sample]
On 03/02/2007, at 2.27, raul diaz wrote:
- Is it possible to show the $1 value in the canvas name: 1_sample
instead of $1_sample? (That's not necessarily but I'm cusious)
You can set the canvas name by
[label new-canvas-name( | [send canvas-receive-symbol]
See attached pd patch for a lill' more detail.