This is intended all right, but on the other hand, perhaps it isn't the right idea in teh first place... is it more useful to have loadbang always called?
The only example I know of is the "loadbang" object, for which it makes no sense to have it emit a "bang" before you connect it to anything...!
Actions to be taken on object creation can be put in the "new" routine. However, perhaps there are examples of actions that should be taken for all new objects, but, if it's being restored from a file, should only happen once the object is fully connected and the rest of the patch is intact. I can't think of any examples of that offhand...
cheers Miller
On Fri, Feb 22, 2002 at 08:45:53AM +0100, Thomas Grill wrote:
Hi Miller,
I'm not sure how Max does it; in Pd you just declare a "loadbang" message and it gets banged (for you to do whatever with.)
yes, loadbang gets triggered when the object's patch is loaded, but it doesn't (in PD) when an object is newly created within an existing patch. Is this intended behavior?
greetings, Thomas