that's also a good point!

it's just that cyclone follows this max logic and we actually did change some of that from the older versions. Some objects in MAX have obligatory arguments and don't create if you don't give it any arguments. In Max that's fine cause you can still call the help file, in Pd you can't. So we're creating the object anyway in cycclone instead.

In this case I agree the best thing to do would be just to let it create with a bad argument.

But hey, it's nice that a DEFSYM doesn't turn "$1" to a float and complains :) it was nice to learn that.

well, thanks again

cheers

Em sáb., 18 de set. de 2021 às 12:38, Christof Ressi <info@christofressi.com> escreveu:

The thing is that when you're designing the abstraction, before it exists, when you're bringing it to life, in its creation process, you might be working on it under the top level,

I see!

and it's annoying to have the object not created.
IMO, there is no reason why an object should refuse to create if you pass bad values for *optional* creation arguments. It's enough to just post an error message, just like when you pass bad values to the corresponding method.

_______________________________________________
Pd-dev mailing list
Pd-dev@lists.iem.at
https://lists.puredata.info/listinfo/pd-dev