You can use class_addcreator to associate any symbol you want with
an object creator.  Then when the user types that symbol into an object
box, it will call the constructor you supplied as an argument to
class_addcreator.

However, the same request for peer pressure applies here: outside of
the cases where aliases are already entrenched, don't use them.  The
small benefit of less typing (or fancy method-sharing) isn't worth the
user-headaches when they fail to instantiate the object.

-Jonathan




On Wednesday, April 6, 2016 6:02 PM, Alexandre Torres Porres <porres@gmail.com> wrote:


in the last thread "Name conflicts "class overwritten; old one renamed 'x_aliased'" I was telling how in cyclone you can compile Line~ with alias names such as "line~" and "cyclone/line~", so you can call these two other versions instead. Other files in cyclone have alias name like Scope~ can be called as "scope~".

But I don't get how this works. The thing is, as i was also trying to clarify in previous threads, I though you could only call and load an alias after I instantiate the object with the official' name.

So, before being able to call "scope~" I'd have to load it as "Scope~". Or load it as "Line~" before "line~" and "cyclone/line~". Or everythiing should have been first loaded as a regular library, then I can call whatever object... I was believing that was the case, and someone like Roman was pending that way as well.

but these objects in cyclone prove wrong, there seems to be a way... but it also sees like some ninja trick with some restrictions, cause I tried renaming one of the aliases from "line~" to "pizza~" and it didn't work. Does it have to do with some 

can anyone shed some light on?

thanks 


_______________________________________________
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list