Re: [PD] Re: namecanvas - why deprecated?
On Sat, Feb 10, 2007 at 09:10:01AM +0100, Frank Barknecht wrote: Chris McCormick hat gesagt: // Chris McCormick wrote: Or maybe you're talking about something else? The namecanvas issue would be solved if each patch was given a default name like pd-$0 or somesuch. That's what I meant: Instead of an object like [namecanvas] that can be deleted, an entry field in an abstraction's Properties menu would be more secure. Ah yes of course, that's a great idea. Chris. --- [EMAIL PROTECTED] http://mccormick.cx ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] Re: namecanvas - why deprecated?
Hallo, Chris McCormick hat gesagt: // Chris McCormick wrote: Or maybe you're talking about something else? The namecanvas issue would be solved if each patch was given a default name like pd-$0 or somesuch. That's what I meant: Instead of an object like [namecanvas] that can be deleted, an entry field in an abstraction's Properties menu would be more secure. Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] re: namecanvas - why deprecated?
Frank Barknecht wrote Try: [clear( | [s $0something] That's why [namecanvas] is not the final word on the functionality it provides. I don't understand what you mean. If you mean because it makes PD crash, then try this: [clear( | [s pd-whateverthisfileiscalled.pd] with no use of [namecanvas]. This crashes too. Actually I don't understand why people are so in love with [namecanvas]. In five or six years of using Pd, I've never written a patch with it. The question is why people are so in love with sending messages to a canvas. I am not either. But if we admit that we have the right to send message to a canvas, then namecanvas is the only way to have (the main canvas of) an instance of an abstraction be assigned a unique name, not shared with other instances. The workaround of creating a subpatch (which you may call $0- or $1-something) is ok if all the dynamically generated stuff is processing stuff, but what if we are dinamically generating interface elements? It is not irrelevant to have to go one level deeper in the patch tree to get a piece of interface visible. I can think of real-life scenarios... ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] Re: namecanvas - why deprecated?
Hallo, Matteo Sisti Sette hat gesagt: // Matteo Sisti Sette wrote: Frank Barknecht wrote Try: [clear( | [s $0something] That's why [namecanvas] is not the final word on the functionality it provides. I don't understand what you mean. If you mean because it makes PD crash, then try this: [clear( | [s pd-whateverthisfileiscalled.pd] with no use of [namecanvas]. This crashes too. Well, that's an error of the patch-author. But clearing a patch containing a [namecanvas] doesn't crash Pd, it just makes the named canvas unavailable for further processing. Attached patch illustrates this behaviour. The workaround of creating a subpatch (which you may call $0- or $1-something) is ok if all the dynamically generated stuff is processing stuff, but what if we are dinamically generating interface elements? It is not irrelevant to have to go one level deeper in the patch tree to get a piece of interface visible. I can think of real-life scenarios... Well, as I mentioned, this is one usecase for namecanvas, that's not possible with subpatches. But it's a usecase, that not necessarily requires a namepatch-object, it is probably better realized with canvas-Properties similar to graph-on-parent etc. Ciao -- Frank Barknecht _ __footils.org_ __goto10.org__ #N canvas 0 0 450 300 10; #X obj 125 113 nc; #X msg 74 59 bang; #X obj 74 140 pack s s; #X msg 74 164 \; \$2 \$1; #X obj 74 84 t b b; #X msg 74 112 clear; #X msg 210 58 bang; #X obj 210 139 pack s s; #X msg 210 163 \; \$2 \$1; #X obj 210 83 t b b; #X msg 210 111 clear; #X obj 261 112 nc; #X connect 0 0 2 1; #X connect 1 0 4 0; #X connect 2 0 3 0; #X connect 4 0 5 0; #X connect 4 1 0 0; #X connect 5 0 2 0; #X connect 6 0 9 0; #X connect 7 0 8 0; #X connect 9 0 10 0; #X connect 9 1 11 0; #X connect 10 0 7 0; #X connect 11 0 7 1; #N canvas 0 0 450 300 10; #X obj 95 72 inlet; #X obj 95 176 outlet; #X obj 158 71 namecanvas \$0-this; #X obj 95 149 symbol \$0-this; #X connect 0 0 3 0; #X connect 3 0 1 0; ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
