2018-01-12 6:28 GMT-02:00 IOhannes m zmölnig zmoelnig@iem.at:
you should simply avoid the nameclash.
I agree that's just the best thing to do, but that is not an option for cyclone.
2018-01-12 6:27 GMT-02:00 IOhannes m zmölnig zmoelnig@iem.at:
no. definitely not. it's "common sense" to allow the user to override vanilla objects.
What I'm saying is Pd vanilla objects have priorities. Yes, you can override vanilla objects, but if you have an [osc~] external in a library and you just call [osc~] in Pd, it'll load the vanilla one. So this is my point, that it is common sense and a very well known behaviour that vanilla objects have priority on the search path.
But I just learned that this doesn't happen for objects in the extra folder. Thus I'm considering it an inconsistent behaviour and in conflict with what we normally have in the Pd world.
Now, if Pd forces a priority for vanilla objects ike [osc~], that doesn't really prevent you from being able to override it, as you mentioned. Hence, forcing a priority on the "extra" folder would not prevent this from happening either. So it's not like you cannot do this otherwise it will ruin everything. People will still be able to override it if they want. All that changes is that it'll be consistent with the current behaviour of Vanilla forcing a search priority for vanilla objects.
cheers