Skip to content
This repository was archived by the owner on Feb 25, 2025. It is now read-only.

Remove single-window assumption from scenario_app#40156

Merged
auto-submit[bot] merged 2 commits intoflutter:mainfrom
goderbauer:migrateScenarioApp
Mar 9, 2023
Merged

Remove single-window assumption from scenario_app#40156
auto-submit[bot] merged 2 commits intoflutter:mainfrom
goderbauer:migrateScenarioApp

Conversation

@goderbauer
Copy link
Member

@goderbauer goderbauer requested a review from loic-sharma March 8, 2023 23:50
@flutter-dashboard
Copy link

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption to this rule, contact Hixie on the #hackers channel in Chat (don't just cc him here, he won't see it! He's on Discord!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

message == 'AppLifecycleState.resumed') {
_nextFrame = _secondFrame;
window.scheduleFrame();
view.platformDispatcher.scheduleFrame();
Copy link
Member

Choose a reason for hiding this comment

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

Hm, one day we may want to schedule a frame for a single view instead of all views. Food for thought, not at all relevant to this change :)

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah, this is something that comes up every now and then. Since we want a unified widget tree, frame scheduling is always gonna be global. There is some discussion on that in https://flutter.dev/go/multiple-views in the Background section.

Copy link
Member

@loic-sharma loic-sharma left a comment

Choose a reason for hiding this comment

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

🚀

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

autosubmit Merge PR when tree becomes green via auto submit App needs tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants