Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Req: Expose default asset resolver in API so a custom resolver can defer to it's implementation #68

Closed
j-stroud opened this issue Sep 30, 2016 · 1 comment

Comments

@j-stroud
Copy link

If one is writing a custom asset resolver and needs similar filesystem behaviour to that provided by the default asset resolver then the Ar_DefaultResolver code needs to be duplicated in the custom implementation.

If the Ar_DefaultResolver class could be exposed as part of the public API then a custom resolver could either derive from or contain an internal instance of this class and defer to it's implementation.

Alternately, if there was API to get the previous 'current' or default asset resolver such that it could be called in the constructor of a custom resolver. e.g. ArGetDefaultResolver().

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants