Sorry, I wasn't being specific-- I'm talking about what happens with [import ekext] or [import pddp]. Aren't these are both examples of "loading a library?"
While it's true [import ekext/polymap] or [declare -lib ekext/polymap] display the console message for [polymap] (the former upon creation and the latter when the patch is opened), that message is only printed once; same for your example below. Iohannes seemed to be implying that a gf.print console message would be a nuisance because the message would get printed for every object used in the patch (minus one, apparently):
"so if you load a patch with 87 [print]'s in there, what information do you get if Pd prints 86 times 'dear user, you are using matju's special [print], which has problems with parens.'"
I don't see how such repeated messages would ever happen-- do you?
My main point is that I think it's a good idea that if an object takes over a vanilla object, the user has some way to know-- for example, to report bugs more effectively. There are plenty of externals that print informative console messages so I don't see why there would be an issue in this case.
-Jonathan
From: Frank Barknecht fbar@footils.org To: pd-list@iem.at Sent: Wed, June 16, 2010 2:24:13 AM Subject: Re: [PD] overriding objects
On Tue, Jun 15, 2010 at 11:46:53AM -0700, Jonathan Wilkes wrote:
Oh, I see, I didn't check about expr. Well, a better example of what I'm talking about would be [polymap] in ekext, as well as (older versions of) [pddplink]. Both post a message about the particular object, both post only once, and both do so by using post in the setup routine for that object. Neither messages are posted when you load the respective libraries. So I'm confused by your example [...]
I rather think you're confused by the term "loading a library". In pd-extended lingo, the term "loading a library" has been misused to also mean setting a couple of "-path"s. The traditional use of the term describes what happens when you use the "-lib" flag or [declare -lib ...]. polymap prints its message, when it's loaded like that:
$ pd -lib polymap ... |. . . . . . . . .polymap. . . . . . . . .| |_- polyphonic chain reaction regulator -_| | . . . . . .Edward Kelly 2006. . . . . . |
Frank
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Wed, 16 Jun 2010, Jonathan Wilkes wrote:
"so if you load a patch with 87 [print]'s in there, what information do you get if Pd prints 86 times 'dear user, you are using matju's special [print], which has problems with parens.'"
BTW, GF's [print] problems have been fixed. Parens such as [print f(x)] are allowed since 9.12, and parens in messages have lost their special meaning as of 9.13.
It took me a long time to do it because I still haven't dealt with some of the consequences of the 9.13 change, but I decided to go ahead anyway because I had postponed it too much, and the negative consequences mostly affect only some lesser-used features, not [print].
I also made a bunch of small changes to make GF's [print] closer to Pd's [print].
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
--- On Thu, 3/24/11, Mathieu Bouchard matju@artengine.ca wrote:
From: Mathieu Bouchard matju@artengine.ca Subject: Re: [PD] overriding objects To: "Jonathan Wilkes" jancsika@yahoo.com Cc: "Frank Barknecht" fbar@footils.org, pd-list@iem.at Date: Thursday, March 24, 2011, 6:50 PM On Wed, 16 Jun 2010, Jonathan Wilkes wrote:
"so if you load a patch with 87 [print]'s in there,
what information do
you get if Pd prints 86 times 'dear user, you are
using matju's special
[print], which has problems with parens.'"
BTW, GF's [print] problems have been fixed. Parens such as [print f(x)] are allowed since 9.12, and parens in messages have lost their special meaning as of 9.13.
It took me a long time to do it because I still haven't dealt with some of the consequences of the 9.13 change, but I decided to go ahead anyway because I had postponed it too much, and the negative consequences mostly affect only some lesser-used features, not [print].
I also made a bunch of small changes to make GF's [print] closer to Pd's [print].
That's actually IOhannes' quote above.
BTW- why was he saying that 87 gf/print objects would print the message 86 times? I thought the message is posted in the setup routine which only gets called when the library is loaded.
-Jonathan
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Thu, 24 Mar 2011, Jonathan Wilkes wrote:
BTW- why was he saying that 87 gf/print objects would print the message 86 times? I thought the message is posted in the setup routine which only gets called when the library is loaded.
No idea, but I'm sorry to have quoted that quote in particular. I just wanted to quote any piece of the original thread, so, I picked the paragraph I stumbled upon in the abyssal depths of one of my inboxes.
I often use my inboxes as near-infinite TODO lists like that. I keep any random mail from a thread as a reminder of something.
Why he said 86 times doesn't matter. It's over.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC