<itemvalue="Scroll physics that does not allow the user to scroll. See also: [ScrollPhysics], which can be used instead of this class when the default behavior is desired instead. [BouncingScrollPhysics], which provides the bouncing overscroll behavior found on iOS. [ClampingScrollPhysics], which provides the clamping overscroll behavior found on Android."/>
<itemvalue="Never Scrollable Scroll Physics"/>
<itemvalue="Bouncing Scroll Physics"/>
<itemvalue="Bouncing Scroll Physics"/>
<itemvalue="Determines the overscroll by applying the boundary conditions. Called by [ScrollPosition.applyBoundaryConditions], which is called by [ScrollPosition.setPixels] just before the [ScrollPosition.pixels] value is updated, to determine how much of the offset is to be clamped off and sent to [ScrollPosition.didOverscrollBy]. The `value` argument is guaranteed to not equal the [ScrollMetrics.pixels] of the `position` argument when this is called. It is possible for this method to be called when the `position` describes an already-out-of-bounds position. In that case, the boundary conditions should usually only prevent a further increase in the extent to which the position is out of bounds, allowing a decrease to be applied successfully, so that (for instance) an animation can smoothly snap an out of bounds position to the bounds. See [BallisticScrollActivity]. This method must not clamp parts of the offset that are entirely within the bounds described by the given `position`. The given `position` is only valid during this method call. Do not keep a reference to it to use later, as the values may update, may not update, or may update to reflect an entirely unrelated scrollable. Examples [BouncingScrollPhysics] returns zero. In other words, it allows scrolling past the boundary unhindered. [ClampingScrollPhysics] returns the amount by which the value is beyond the position or the boundary, whichever is furthest from the content. In other words, it disallows scrolling past the boundary, but allows scrolling back from being overscrolled, if for some reason the position ends up overscrolled."/>
<itemvalue="Determines the overscroll by applying the boundary conditions. Called by [ScrollPosition.applyBoundaryConditions], which is called by [ScrollPosition.setPixels] just before the [ScrollPosition.pixels] value is updated, to determine how much of the offset is to be clamped off and sent to [ScrollPosition.didOverscrollBy]. The `value` argument is guaranteed to not equal the [ScrollMetrics.pixels] of the `position` argument when this is called. It is possible for this method to be called when the `position` describes an already-out-of-bounds position. In that case, the boundary conditions should usually only prevent a further increase in the extent to which the position is out of bounds, allowing a decrease to be applied successfully, so that (for instance) an animation can smoothly snap an out of bounds position to the bounds. See [BallisticScrollActivity]. This method must not clamp parts of the offset that are entirely within the bounds described by the given `position`. The given `position` is only valid during this method call. Do not keep a reference to it to use later, as the values may update, may not update, or may update to reflect an entirely unrelated scrollable. Examples [BouncingScrollPhysics] returns zero. In other words, it allows scrolling past the boundary unhindered. [ClampingScrollPhysics] returns the amount by which the value is beyond the position or the boundary, whichever is furthest from the content. In other words, it disallows scrolling past the boundary, but allows scrolling back from being overscrolled, if for some reason the position ends up overscrolled."/>
<itemvalue="allow Implicit Scrolling"/>
<itemvalue="Update the scroll position ([pixels]) to a given pixel value. This should only be called by the current [ScrollActivity], either during the transient callback phase or in response to user input. Returns the overscroll, if any. If the return value is 0.0, that means that [pixels] now returns the given `value`. If the return value is positive, then [pixels] is less than the requested `value` by the given amount (overscroll past the max extent), and if it is negative, it is greater than the requested `value` by the given amount (underscroll past the min extent). The amount of overscroll is computed by [applyBoundaryConditions]. The amount of the change that is applied is reported using [didUpdateScrollPositionBy]. If there is any overscroll, it is reported using [didOverscrollBy]."/>
<itemvalue="Update the scroll position ([pixels]) to a given pixel value. This should only be called by the current [ScrollActivity], either during the transient callback phase or in response to user input. Returns the overscroll, if any. If the return value is 0.0, that means that [pixels] now returns the given `value`. If the return value is positive, then [pixels] is less than the requested `value` by the given amount (overscroll past the max extent), and if it is negative, it is greater than the requested `value` by the given amount (underscroll past the min extent). The amount of overscroll is computed by [applyBoundaryConditions]. The amount of the change that is applied is reported using [didUpdateScrollPositionBy]. If there is any overscroll, it is reported using [didOverscrollBy]."/>
<itemvalue="'{physics.runtimeType}.applyBoundaryConditions returned invalid overscroll value.\n' 'The method was called to consider a change from pixels to value, which is a ' 'delta of {delta.toStringAsFixed(1)} units. However, it returned an overscroll of ' '{result.toStringAsFixed(1)} units, which has a greater magnitude than the delta. ' 'The applyBoundaryConditions method is only supposed to reduce the possible range ' 'of movement, not increase it.\n' 'The scroll extents are minScrollExtent .. maxScrollExtent, and the ' 'viewport dimension is viewportDimension.',"/>
<itemvalue="'{physics.runtimeType}.applyBoundaryConditions returned invalid overscroll value.\n' 'The method was called to consider a change from pixels to value, which is a ' 'delta of {delta.toStringAsFixed(1)} units. However, it returned an overscroll of ' '{result.toStringAsFixed(1)} units, which has a greater magnitude than the delta. ' 'The applyBoundaryConditions method is only supposed to reduce the possible range ' 'of movement, not increase it.\n' 'The scroll extents are minScrollExtent .. maxScrollExtent, and the ' 'viewport dimension is viewportDimension.',"/>
<itemvalue="Called by [setPixels] to report overscroll when an attempt is made to change the [pixels] position. Overscroll is the amount of change that was not applied to the [pixels] value."/>
<itemvalue="Called by [setPixels] to report overscroll when an attempt is made to change the [pixels] position. Overscroll is the amount of change that was not applied to the [pixels] value."/>
@ -51,14 +54,11 @@
<itemvalue="update default avatar assets."/>
<itemvalue="update default avatar assets."/>
<itemvalue="Waits for multiple futures to complete and collects their results. Returns a future which will complete once all the provided futures have completed, either with their results, or with an error if any of the provided futures fail. The value of the returned future will be a list of all the values that were produced in the order that the futures are provided by iterating [futures]. If any future completes with an error, then the returned future completes with that error. If further futures also complete with errors, those errors are discarded. If `eagerError` is true, the returned future completes with an error immediately on the first error from one of the futures. Otherwise all futures must complete before the returned future is completed (still with the first error; the remaining errors are silently dropped). In the case of an error, [cleanUp] (if provided), is invoked on any non-null result of successful futures. This makes it possible to `cleanUp` resources that would otherwise be lost (since the returned future does not provide access to these values). The [cleanUp] function is unused if there is no error. The call to [cleanUp] should not throw. If it does, the error will be an uncaught asynchronous error. @pragma("vm:recognized", "other")"/>
<itemvalue="Waits for multiple futures to complete and collects their results. Returns a future which will complete once all the provided futures have completed, either with their results, or with an error if any of the provided futures fail. The value of the returned future will be a list of all the values that were produced in the order that the futures are provided by iterating [futures]. If any future completes with an error, then the returned future completes with that error. If further futures also complete with errors, those errors are discarded. If `eagerError` is true, the returned future completes with an error immediately on the first error from one of the futures. Otherwise all futures must complete before the returned future is completed (still with the first error; the remaining errors are silently dropped). In the case of an error, [cleanUp] (if provided), is invoked on any non-null result of successful futures. This makes it possible to `cleanUp` resources that would otherwise be lost (since the returned future does not provide access to these values). The [cleanUp] function is unused if there is no error. The call to [cleanUp] should not throw. If it does, the error will be an uncaught asynchronous error. @pragma("vm:recognized", "other")"/>
<itemvalue="Add delay before hide skeletons."/>
<itemvalue="Add delay before hide skeletons."/>
<itemvalue="repeat"/>
<itemvalue="Creates an animation controller with no upper or lower bound for its value. [value] is the initial value of the animation. [duration] is the length of time this animation should last. [debugLabel] is a string to help identify this animation during debugging (used by [toString]). `vsync` is the [TickerProvider] for the current context. It can be changed by calling [resync]. It is required and must not be null. See [TickerProvider] for advice on obtaining a ticker provider. This constructor is most useful for animations that will be driven using a physics simulation, especially when the physics simulation has no pre-determined bounds."/>
