-
Notifications
You must be signed in to change notification settings - Fork 17
Support partial window #98
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
Support partial window #98
Conversation
597fe55
to
1a71e39
Compare
After #90, we use Chromium style |
1a71e39
to
bc54a13
Compare
* This is a necessary feature for partial window. Signed-off-by: MuHong Byun <[email protected]>
bc54a13
to
56c9c35
Compare
Thanks for your tip. |
I don't know about this scenario, but I'm curious what's the reason to create the window outside embedder? |
Considering various situations, multi-screen support in Flutter is still in early stage. So.. using multiple windows and |
Could you share your findings on this, why you're using this approach (creating a window in the app side), and what you're eventually going to implement (overall design) in #94 as an issue comment (not here)? I don't understand how this change is even related to multi-window support so far. |
First of all, I'm sorry that there wasn't much explanation. |
I checked the android sample, it is showing sample of enginegroup, which share resources when multiple engines exist, but I still don't understand why create a window in app, instead of using the window inside embedder. |
Could we move the discussion to #94? 🙂 |
Go on #114 |
Preparation work for #94