Building an application for a desktop platform that transitively included any Dart-based plugins (such as path_provider) broke `flutter test`, because its compilation was overriding the provided main (in this case, the test main) with `generated_main.dart` if it was present. This PR:
- Changes the `flutter test` compilation path to update `generated_main.dart`, so that the tests will work, and will include any registered Dart plugins.
- Makes using `generated_main.dart` during recompile opt-in, to try to reduce the chance of a similar bug happening with other codepaths in the future.
Fixes https://github.com/flutter/flutter/issues/88794
I've added a Focus.withExternalFocusNode constructor to the Focus widget (and the FocusScope widget) that makes it explicit that the widget's attributes won't affect the settings of the given focus node.
This is to help address #83023, which is a snag in the API that people run into occasionally.
This should help make it explicit when you want the widget attributes to take precedence, and when you don't.
This modifies the flutter update-packages and flutter update-packages --force-upgrade commands so that the many invocations of "dart pub get" in each repo project run in parallel instead of in series.
* Initial layout and theme
* fixed tests
* made page scrollable
* fixes based on Chris on Casey's comments
* removed desktop_window, add errorWidget
* 2nd round of fixes
* fixed linux analyze
* changes based on Casey's comments:
* remove trailing space
* removed obselete macos build code
* add discrepency in project.pbxproj
* addressed Casey's comment
* 1b5b3c0b0 Roll Skia from 43264640f256 to 791c0d36a6f6 (2 revisions) (flutter/engine#28909)
* d3f17b01d Mirror master to main branch. (flutter/engine#28896)
* 8f964925e Roll Dart SDK from f452a6585cbd to 280a0c3efb21 (1 revision) (flutter/engine#28910)
* 0aee3c6d1 Roll Skia from 791c0d36a6f6 to 0f124cd7cd60 (2 revisions) (flutter/engine#28911)
* bd250bdd8 Windows: Add dark theme support. (flutter/engine#28131)
This adjusts the size of the delete button so that it takes up just slightly less than half of the chip, so that legacy tests that tap on the center of the chip still hit the chip, and not the delete button.
A follow-on change for #90531
In the process of fixing #90044, I realized that it's also possible for hovered tooltips to show more than one at a time if the widgets are nested, so this PR is a fix that prevents more than one tooltip from showing at a time with hovered tooltips.
This adds a smoke test for every single API example. It also fixes 17 tests that had bugs in them, or were otherwise broken, and even fixes one actual bug in the framework, and one limitation in the framework.
The bug in the framework is that NetworkImage's _loadAsync method had await response.drain<List<int>>();, but if the response is null, it will throw a cryptic exception saying that Null can't be assigned to List<int>. The fix was just to use await response.drain<void>(); instead.
The limitation is that RelativePositionedTransition takes an Animation<Rect> rect parameter, and if you want to use a RectTween with it, the value emitted there is Rect?, and one of the examples was just casting from Animation<Rect> to Animation<Rect?>, which is invalid, so I modified RelativePositionedTransition to take a Rect? and just use Rect.zero if the rect is null.
