by chrisjj » Wed May 12, 2010 1:21 pm
> This discussion is sufficient as a wish, just file it in Mantis in the Wishlist section and link between here and Mantis.
OK.
> I wonder though can you guarantee that no script, plugin, addon, user will be effected by the requested change?
Good point! But the change should be just an additional method or perhaps class, so would not affect the existing API. But of course since there will be change to the code, there is teh same as always possibility of disturbing any existing unstable code.
I don't have sufficient understanding of the the API to suggest how the best solution. What would you propose? E.g. what is the best precedent in the API for referencing a node property that is an object other than a collection of tracks?
> This discussion is sufficient as a wish, just file it in Mantis in the Wishlist section and link between here and Mantis.
OK.
> I wonder though can you guarantee that no script, plugin, addon, user will be effected by the requested change?
Good point! But the change should be just an additional method or perhaps class, so would not affect the existing API. But of course since there will be change to the code, there is teh same as always possibility of disturbing any existing unstable code.
I don't have sufficient understanding of the the API to suggest how the best solution. What would you propose? E.g. what is the best precedent in the API for referencing a node property that is an object other than a collection of tracks?