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
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
