- Create an abstraction with the same name as a built-in object or an object loaded through a library (adsr~ for example)
- Create tooltip labels via arguments in the [inlet] and [outlet] objects
-> tooltip labels reflect the built-in, not the abstraction
This happens silently, so the result is that if someone creates an object with the same name, either intentionally or inadvertently, the connections will be mislabeled.
It came up for me because I am making shadow objects of some uncompilable objects, which I think is a legit use of overriding names -- especially since I'm putting these in the Externals folder in their own namespace (eg, ac/adsr~), but specifying the full path doesn't solve the issue.
-> tooltip labels reflect the built-in, not the abstraction
This happens silently, so the result is that if someone creates an object with the same name, either intentionally or inadvertently, the connections will be mislabeled.
It came up for me because I am making shadow objects of some uncompilable objects, which I think is a legit use of overriding names -- especially since I'm putting these in the Externals folder in their own namespace (eg, ac/adsr~), but specifying the full path doesn't solve the issue.