<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;"><div id="yiv951509556"><div id="yiv85026924"><style type="text/css"><!--#yiv951509556 #yiv85026924 DIV {margin:0px;}--></style><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">Sorry, I wasn't being specific-- I'm talking about what happens with [import ekext] <br>or [import pddp]. Aren't these are both examples of "loading a library?"<br><br>While it's true [import ekext/polymap] or [declare -lib ekext/polymap] display<br>the console message for [polymap] (the former upon creation and the latter when <br>the patch is opened), that message is only printed once; same for your <br>example below. Iohannes seemed to be implying that a gf.print console message <br>would be a nuisance because the message would get printed for every object used
<br>in the
patch (minus one, apparently):<br><br>"so if you load a patch with 87 [print]'s in there, what information do<br>you
get if Pd prints 86 times 'dear user\, you are using matju's special<br>[print]\,
which has problems with parens.'"<br><br>I don't see how such repeated messages would ever happen-- do you?<br><br>My main point is that I think it's a good idea that if an object takes over a vanilla <br>object, the user has some way to know-- for example, to report bugs more <br>effectively. There are plenty of externals that print informative console <br>messages so I don't see why there would be an issue in this case.<br><br>-Jonathan<br><br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Frank Barknecht <fbar@footils.org><br><b><span style="font-weight: bold;">To:</span></b> pd-list@iem.at<br><b><span style="font-weight: bold;">Sent:</span></b> Wed, June 16, 2010 2:24:13 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [PD] overriding objects<br></font><br>
On Tue, Jun 15, 2010 at 11:46:53AM -0700, Jonathan Wilkes wrote:<br>> Oh, I see, I didn't check about expr. Well, a better example of what<br>> I'm talking about would be [polymap] in ekext, as well as (older<br>> versions of) [pddplink]. Both post a message about the particular<br>> object, both post only once, and both do so by using post in the setup<br>> routine for that object. Neither messages are posted when you load<br>> the respective libraries. So I'm confused by your example [...]<br><br>I rather think you're confused by the term "loading a library". In<br>pd-extended lingo, the term "loading a library" has been misused to also<br>mean setting a couple of "-path"s. The traditional use of the term<br>describes what happens when you use the "-lib" flag or [declare -lib<br>...]. polymap prints its message, when it's loaded like that:<br><br> $ pd -lib polymap<br> ...<br>
|. . . . . . . . .polymap. . . . . . . . .|<br> |_- polyphonic chain reaction regulator -_|<br> | . . . . . .Edward Kelly 2006. . . . . . |<br><br>Ciao<br>-- <br>Frank<br><br>_______________________________________________<br><a rel="nofollow">Pd-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list<br></div></div>
</div></div></div></td></tr></table><br>