- 17 Aug, 2022 1 commit
-
-
yaakovschectman authored
* Add Windows startup test * Add new tests for Windows desktop * Bring up complex layout tests for Win Desktop * Bring up flutter_view startup test for Windows * Add Platform View startup test for Windows * Fix typo in .ci.yaml * Make basename variable final * Link to bug in .ci.yaml
-
- 07 Jun, 2021 1 commit
-
-
Jason Simmons authored
-
- 28 Sep, 2020 1 commit
-
-
Jonah Williams authored
Check in linux and windows platform code now that they are stable, so that we could use in devicelab in the future. Removed the ICO from the windows example to avoid analysis check, and since it won't be important for benchmarking or UI tests
-
- 15 Sep, 2020 1 commit
-
-
stuartmorgan authored
-
- 21 Aug, 2020 1 commit
-
-
stuartmorgan authored
This wires up the new WindowProc delegation system that allows plugins to handle top-level window messages (e.g., to control resize behavior). Fixes #53168
-
- 13 Aug, 2020 1 commit
-
-
stuartmorgan authored
-
- 06 Apr, 2020 1 commit
-
-
stuartmorgan authored
This moves the app template more toward being a more generic starting point for any Flutter application, eliminating some hard-code assumptions about there being a single window/engine pair that is directly bound to the life of the application: - Moves the runloop into its own class, making it capable of servicing any number of engine instances. - Moves the logic for setting up a window containing only a Flutter view into a window subclass for ease of re-use. - Makes quit-on-window-close an optional property. (Long term this should be even more generic, like a quit-when-last-window-closes option, but this is a short-term improvement that removes the binding between the runloop and the window). - Allows for multiple instances of Win32Window to exist without issues relating to the window class registration. Since there are getting to be a non-trivial number of files associated with the runner, this moves the source into a runner/ directory, as is already done on some other platforms. Note that creating multiple Flutter windows at the same time still doesn't work correctly even with this change, but this addresses some of the known issues, and makes it easier to test in the future (e.g., for debugging engine-level issues with multiple instances). Fixes #45397
-