-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Disable smooth resizing when UI and platform threads are merged. #172835
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
Disable smooth resizing when UI and platform threads are merged. #172835
Conversation
We can't get this without returning the thread to Flutter, thus breaking the GTK draw update.
|
@knopp any ideas on how to do smooth resizing with merged threads? Would it be possible for the embedder to call into the engine to do the update in this case? |
|
This should be possible by pumping (only) flutter event loop messages instead of I'm having my laptop serviced this week (hopefully), once it is back I can give it a shot. |
mattkae
left a comment
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.
I have one nit, but I will defer to @knopp on the specifics of the thread merging here
| FlCompositorSoftware* fl_compositor_software_new(FlEngine* engine) { | ||
| FlCompositorSoftware* self = FL_COMPOSITOR_SOFTWARE( | ||
| g_object_new(fl_compositor_software_get_type(), nullptr)); | ||
| self->smooth_resize = !fl_engine_get_has_ui_on_platform_thread(engine); |
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.
Nit: Why not pass smooth_resize as a bool to the constructor instead of passing the entire engine?
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.
I did this for consistency with the OpenGL compositor mostly. I was also thinking this - are we asking the compositor to do smooth resizing or is the compositor deciding if it is capable? (This is what I ended up with). I think we'll be able to remove this in the future so it's probably not a big issue.
|
Fixed in #172893 |
|
Warning There is an error in the Gemini Code Assist config file for this repository at |
We can't get this without returning the thread to Flutter, thus breaking the GTK draw update.