-
Notifications
You must be signed in to change notification settings - Fork 6k
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
[android] Add HC++ platform view controller. #56776
base: main
Are you sure you want to change the base?
Conversation
@@ -1129,7 +1129,8 @@ public void attachToFlutterEngine(@NonNull FlutterEngine flutterEngine) { | |||
this, | |||
this.flutterEngine.getTextInputChannel(), | |||
this.flutterEngine.getScribeChannel(), | |||
this.flutterEngine.getPlatformViewsController()); | |||
this.flutterEngine.getPlatformViewsController(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unrelated to your change- would probably be simpler to just pass flutterEngine into this call?
This pull request executed golden file tests, but it has not been updated in a while (20+ days). Test results from Gold expire after as many days, so this pull request will need to be updated with a fresh commit in order to get results from Gold. |
Hybrid composition++ has an entirely different mechanism for compositing than the previous approach. To that end, its much simpler to devise a second platform view controller than to add a 4th mechanism to the existing nightmare class.
This change does not actually wire up the new platform view controller to the engine, nor does it add a mechanism for enabling/disabling the new platform views code. This logic should be mostly inert, but I'd prefer to start checking it in now.