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

Bring back ASInitializeFrameworkMainThread so we don't break the API #2050

Merged
merged 1 commit into from
Dec 6, 2021

Conversation

rcancro
Copy link
Contributor

@rcancro rcancro commented Dec 6, 2021

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 with ASInitializeFrameworkMainThreadOnConstructor and ASInitializeFrameworkMainThreadOnDestructor. This should keep the old functionality in place for any client using ASInitializeFrameworkMainThread directly.

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 with `ASInitializeFrameworkMainThreadOnConstructor` and `ASInitializeFrameworkMainThreadOnDestructor`. This should keep the old functionality in place for any client using `ASInitializeFrameworkMainThread` directly.
@rcancro rcancro merged commit 50426db into TextureGroup:master Dec 6, 2021
@rcancro rcancro deleted the initMain branch December 6, 2021 22:32
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

Successfully merging this pull request may close these issues.

None yet

2 participants