To solve the problem of window losing response caused by MoveWindow#76973
To solve the problem of window losing response caused by MoveWindow#76973tilongzs wants to merge 1 commit intoflutter:devfrom tilongzs:dev
Conversation
…the size of sub window is changed by PostMessage.
|
This pull request is trying merge the branch dev, which is the name of a release branch. This is usually a mistake. See Tree Hygiene for detailed instructions on how to contribute to the Flutter project. In particular, ensure that before you start coding, you create your feature branch off of master. This PR has been closed. If you are sure you want to merge dev, you may re-open this issue. |
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
|
@googlebot I signed it! |
In windows desktop projects, the window loses its response when the MoveWindow function of win32 is called directly from the Flutter interface. It is suspected WM_SIZE the modification of the sub-window in the message.

I raised this issue in the win32 plug-in project, and it has been agreed that this is not a win32 plug-in issue.
(halildurmus/win32#157)
I found a solution. By modifying the (windows\runner\win32_window.cpp) file, create a custom message that delays the code WM_SIZE the modified sub-window in "Windows".