This PR adds a SweepGradient class, extending Gradient to expose the engine's ui.Gradient.sweep shader.
Similar to LinearGradient and RadialGradient - SweepGradients can be used in a BoxDecoration or passed to a Paint's shader.
https://github.com/flutter/flutter/issues/17956
* Add a `debugInstrumentAction()` method that will wrap an action
in a stopwatch and print the time it took to run the action.
* Add a global `debugInstrumentationEnabled` that will control
whether `debugInstrumentAction()` does anything (even in debug
builds).
* Add some basic instrumentation to `registerServiceExtension()`
* Temporarily enable the `debugInstrumentationEnabled` flag in the
Gallery to give us better visibility into what's happening in
https://github.com/flutter/flutter/issues/17956
It should be calling `tile.getDistanceToActualBaseline()` rather than
`tile.getDistanceToBaseline()`. This is causing us to hit assertions
`getDistanceToBaseline()`
* Fix#16464: Pass hit test when a big child is inside RenderFittedBox, RenderTransform, RenderFractionalTranslation, or RenderFollowerLayer
* Override `hitTestChildren`
* RenderTransform and RenderFollowerLayer shouldn't check if they are hit
themselves
* Test the hit test for translated child into translated box
* Add hit test for `FractionalTranslation`
* Don't check if RenderFractionalTranslation is hit themself
* Add hit test for FractionalTranslation
* Add test for FractionalTranslation
This optimizes the AnimatedSwitcher so that it tags the right widget with its keyed subtree, and avoids rebuilding the transition unnecessarily.
This significantly improves the performance of Chips (which uses AnimatedSwitcher to swap out it's avatar and delete icon children).
This is a follow up on issue #17169 and the pull request #17298
This pull request adds the onChangeStart and onChangeEnd callbacks for CupertinoSlider. These are called when a user starts and ends a change respectively.
Pushing for @dcaraujo0872, the PR author.
Our style guide says the k's are not necessary, and it seems like a good idea to make all the code be consistent on this.
Only naming changes to private vars: no logic changes.
I'm moving the assets in the assets-for-api-docs repo to a slightly different location to help with organization in that repo, so this PR points the doc URLs to the new location. The old assets won't be removed until this PR makes its way to the API docs website.
No documentation or code changes here, other than changing doc image URLs.
This adds a simple spacer widget first suggested by Scott Stoll (@ScottS2017) in the abandoned PR #15802
This PR replaces that one, cleans it up, and adds a test.
