hi all,
this is actually another bug report :)
Krzysztof
#N canvas 10 10 500 450 12; #X obj 25 20 loadbang; #X msg 25 60 1 0 1 2 0 1; #X obj 25 100 unpack 0 0 0 0 0 0; #X obj 25 140 makefilename $%d; #X obj 25 180 spigot; #X obj 100 180 spigot; #X obj 25 220 pack s s; #X msg 25 260 ; pd-whoami.pd obj 200 20 unknown printme not ; pd filename dont-you-know? . ; #N canvas ; #X obj 25 20 r $1 ; #X obj 25 60 print $2 ; #X connect 0 0 1 0 ; #X pop 1 ; printme nn ; #X connect 0 0 1 0; #X connect 1 0 2 0; #X connect 2 0 3 0; #X connect 2 1 5 1; #X connect 2 2 4 1; #X connect 2 3 3 0; #X connect 2 4 4 1; #X connect 2 5 5 1; #X connect 3 0 4 0; #X connect 3 0 5 0; #X connect 4 0 6 0; #X connect 5 0 6 1; #X connect 6 0 7 0;
Hi all,
Well, here I am finally finishing June up...
This is a funny situation, where Pd's internal state (the current arguments to the "unknown" object) fight with an attempt to build a patch from a message box. I think there is much work to do to get this working properly, but anyway, I think it's not a really important feature. If people _do_ want to make patches that build patches, the most robust way is to use the "textfile" object to build the patch and then load it from the filesystem.
For people wanting to add objects to patches and connect/disconnect them by messages, I'm planning someday to make a "select-region" message to a Pd so that if you know where an object is on the screen you can select and delete it.
But there's much more urgent stuff I want to get to first...
cheers Miller
On Tue, Jun 26, 2001 at 04:19:54PM +0200, Krzysztof Czaja wrote:
hi all,
this is actually another bug report :)
Krzysztof #N canvas 10 10 500 450 12; #X obj 25 20 loadbang; #X msg 25 60 1 0 1 2 0 1; #X obj 25 100 unpack 0 0 0 0 0 0; #X obj 25 140 makefilename $%d; #X obj 25 180 spigot; #X obj 100 180 spigot; #X obj 25 220 pack s s; #X msg 25 260 ; pd-whoami.pd obj 200 20 unknown printme not ; pd filename dont-you-know? . ; #N canvas ; #X obj 25 20 r $1 ; #X obj 25 60 print $2 ; #X connect 0 0 1 0 ; #X pop 1 ; printme nn ; #X connect 0 0 1 0; #X connect 1 0 2 0; #X connect 2 0 3 0; #X connect 2 1 5 1; #X connect 2 2 4 1; #X connect 2 3 3 0; #X connect 2 4 4 1; #X connect 2 5 5 1; #X connect 3 0 4 0; #X connect 3 0 5 0; #X connect 4 0 6 0; #X connect 5 0 6 1; #X connect 6 0 7 0;
hi,
then why not to set those would-be abstraction arguments only after it is known that .pd file exists? See my post from Sat, 22 Sep 2001 19:22:18 +0200
But yes, this is just a funny behaviour, not really important.
Miller Puckette wrote: ...
This is a funny situation, where Pd's internal state (the current arguments to the "unknown" object) fight with an attempt to build a patch from a message box. I think there is much work to do to get this working properly,
Krzysztof
ps...
For people wanting to add objects to patches and connect/disconnect them by messages, I'm planning someday to make a "select-region" message to a Pd so that if you know where an object is on the screen you can select and delete it.
it is already there, in a way -- there are click',
find' and `cut'
messages to a canvas.