Bring back ASInitializeFrameworkMainThread so we don't break the API #2050
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In PR 2032 we added alloc/dealloc texture initialization methods for the case where texture is automatically initializing. However, in doing so we have removed the
ASInitializeFrameworkMainThread
method that clients may already be using.This PR brings back the
ASInitializeFrameworkMainThread
to live side by side withASInitializeFrameworkMainThreadOnConstructor
andASInitializeFrameworkMainThreadOnDestructor
. This should keep the old functionality in place for any client usingASInitializeFrameworkMainThread
directly.