To solve the problem of window losing response caused by MoveWindow #76973
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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".