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
Implement a Win32/UWP desktop shell #30726
Comments
CC @clarkezone who is working on this. |
For cross-referencing, #14967 is general umbrella feature request for UWP. I'll leave this open separately since this is specifically tracking an initial shell implementation rather than the overall support. |
As UWP developer, I am waiting GG support UWP too much |
Start work on flutter/flutter#30726 by adding an alternative win32 shell platform implementation for Windows that is not based on GLFW and that uses LIBANGLE for rendering and native win32 windowing and input. This change does not replace the GLFW implementation but rather runs side by side with it producing a secondary flutter_windows_win32.dll artifact. The following items must be added to attain parity with the GLFW implementation: - Custom task scheduling - Support for keyboard modifier keys - Async texture uploads - Correct high DPI handling on Windows versions < 1703 and will be added in subsequent changes.
This actually should have been closed when the last PR above landed; we're now using a Win32 shell rather than the GLFW shell. #14967 continues to track UWP specifically. |
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of |
The current implementation on Windows is a temporary solution using GLFW; the goal is to implement a more flexible, view-based solution that could be used in an existing application, similar to what currently exists on macOS.
See previous discussion in google/flutter-desktop-embedding#6 and google/flutter-desktop-embedding#101.
The text was updated successfully, but these errors were encountered: