After Load prim...

[oddson]

...I need to think some more about this but one solution would be to create a new component to cover these other situations - a kind of 'After Duplicate' component if you like.

Or you could make AfterLoad work the way both you and aliasant thought it should... I can't see that this would break anything for anyone.

[infuzion]

...I need to think some more about this but one solution would be to create a new component to cover these other situations - a kind of 'After Duplicate' component if you like.

Or you could make AfterLoad work the way both you and aliasant thought it should... I can't see that this would break anything for anyone.

I find extra triggers annoying, so I'd be against this. I imagine I could live with it. Or have the "After Load trigger with placement also []" in the options is anther idea.

[oddson]

...I find extra triggers annoying, so I'd be against this...

But it would only fire a trigger when you paste something with an AfterLoad primitive in it... it would otherwise change nothing on existing schematics...

I love new primitives but only when they do something useful.

[DigitalWhiteByte]

I think that might be useful to have a primary that would give a trig,
when it is taken from the toolbox, because when the block of the module will work,
could be used to initialize some function in it. To me it seems useful.

[oddson]

But what I'm saying is that useful thing could be done by the same very useful AlfterLoad primitive which would only fire the extra trigger in the very specific circumstance of when it's pasted as part of a module...

But if there's a new primitive all it would be good for is on pasting to initialize parameter settings, but chances are you'd also need to add an AfterLoad to make sure they also initialize on loading the VST/exe... why not do both with the same one... which is what Aliasant expected in the first place and what Malc assumed it would do.

[aliasant]

But what I'm saying is that useful thing could be done by the same very useful AlfterLoad primitive which would only fire the extra trigger in the very specific circumstance of when it's pasted as part of a module...

But if there's a new primitive all it would be good for is on pasting to initialize parameter settings, but chances are you'd also need to add an AfterLoad to make sure they also initialize on loading the VST/exe... why not do both with the same one... which is what Aliasant expected in the first place and what Malc assumed it would do.

(meaningless comment from a tired, pretty much useless brain not yet had its coffe.... )