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

async -> sync #1006

Closed
wants to merge 1 commit into from
Closed

async -> sync #1006

wants to merge 1 commit into from

Conversation

if (mCurrentTransaction == null) {
mCurrentTransaction = mFragmentManager.beginTransaction();
mCurrentTransaction.setReorderingAllowed(true);
if (mCurrentTransaction != null) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this seems to no longer be necessary if we create new transaction and then commit it with each single operation. As a consequence we wouldn't need the mCurrentTransaction field nor need to call getOrCreaeTransaction nor tryCommitTransaction

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it was left for usage with ScreenStack, where we have animations in Fragments, so we want to concatenate all the operations into one and run animations on them. Btw, I would change the name commitNowAllowingStateLoss to something like commitTransaction.

@WoLewicki
Copy link
Member

Closed in favor of #1066.

@WoLewicki WoLewicki closed this Sep 8, 2021
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

3 participants