<itemvalue="Creates an image filter that applies a matrix transformation. For example, applying a positive scale matrix (see [Matrix4.diagonal3]) when used with [BackdropFilter] would magnify the background image."/>
<itemvalue="Composes the `inner` filter with `outer`, to combine their effects. Creates a single [ImageFilter] that when applied, has the same effect as subsequently applying `inner` and `outer`, i.e., result = outer(inner(source))."/>
<itemvalue="[BackdropFilter], a widget that applies [ImageFilter] to its rendering. [ImageFiltered], a widget that applies [ImageFilter] to its children. [SceneBuilder.pushBackdropFilter], which is the low-level API for using this class as a backdrop filter. [SceneBuilder.pushImageFilter], which is the low-level API for using this class as a child layer filter."/>
<itemvalue="Whether this entry occludes the entire overlay. If an entry claims to be opaque, then, for efficiency, the overlay will skip building entries below that entry unless they have [maintainState] set."/>
<itemvalue="_status Bar Hidded"/>
<itemvalue="_status Bar Hidden"/>
<itemvalue="maintain State"/>
<itemvalue="opaque"/>
<itemvalue="Schedule a callback for the end of this frame. Does not request a new frame. This callback is run during a frame, just after the persistent frame callbacks (which is when the main rendering pipeline has been flushed). If a frame is in progress and post-frame callbacks haven't been executed yet, then the registered callback is still executed during the frame. Otherwise, the registered callback is executed during the next frame. The callbacks are executed in the order in which they have been added. Post-frame callbacks cannot be unregistered. They are called exactly once. See also: [scheduleFrameCallback], which registers a callback for the start of the next frame."/>
<itemvalue="Fullscreen display with status and navigation elements rendered over the application. Available starting at SDK 29 or Android 10. Earlier versions of Android will not be affected by this setting. For applications running on iOS, the status bar and home indicator will be visible. The system overlays will not disappear or reappear in this mode as they are permanently displayed on top of the application. See also: [SystemUiOverlayStyle], can be used to configure transparent status and navigation bars with or without a contrast scrim."/>
<itemvalue="Specifies the [SystemUiMode] to have visible when the application is running. The `overlays` argument is a list of [SystemUiOverlay] enum values denoting the overlays to show when configured with [SystemUiMode.manual]. If a particular mode is unsupported on the platform, enabling or disabling that mode will be ignored. The settings here can be overridden by the platform when System UI becomes necessary for functionality. For example, on Android, when the keyboard becomes visible, it will enable the navigation bar and status bar system UI overlays. When the keyboard is closed, Android will not restore the previous UI visibility settings, and the UI visibility cannot be changed until 1 second after the keyboard is closed to prevent malware locking users from navigation buttons. To regain "fullscreen" after text entry, the UI overlays can be set again after a delay of at least 1 second through [restoreSystemUIOverlays] or calling this again. Otherwise, the original UI overlay settings will be automatically restored only when the application loses and regains focus. Alternatively, a [SystemUiChangeCallback] can be provided to respond to changes in the System UI. This will be called, for example, when in [SystemUiMode.leanBack] and the user taps the screen to bring up the system overlays. The callback provides a boolean to represent if the application is currently in a fullscreen mode or not, so that the application can respond to these changes. When `systemOverlaysAreVisible` is true, the application is not fullscreen. See [SystemChrome.setSystemUIChangeCallback] to respond to these changes in a fullscreen application."/>
<itemvalue="Declares manually configured [SystemUiOverlay]s. When using this mode with [SystemChrome.setEnabledSystemUIMode], the preferred overlays must be set by the developer. When [SystemUiOverlay.top] is enabled, the status bar will remain visible on all platforms. Omitting this overlay will hide the status bar on iOS & Android. When [SystemUiOverlay.bottom] is enabled, the navigation bar and home indicator of Android and iOS applications will remain visible. Omitting this overlay will hide them. Omitting both overlays will result in the same configuration as [SystemUiMode.leanBack]."/>
<itemvalue="Fullscreen display with status and navigation bars presentable through a swipe gesture at the edges of the display. Available starting at SDK 19 or Android K. Earlier versions of Android will not be affected by this setting. For applications running on iOS, the status bar and home indicator will be hidden for a similar fullscreen experience. A swipe gesture from the edge of the screen displays overlays. In contrast to [SystemUiMode.immersiveSticky], this gesture is not received by the application. See also: [SystemUiChangeCallback], used to listen and respond to the change in system overlays."/>
<itemvalue="Fullscreen display with status and navigation bars presentable by tapping anywhere on the display. Available starting at SDK 16 or Android J. Earlier versions of Android will not be affected by this setting. For applications running on iOS, the status bar and home indicator will be hidden for a similar fullscreen experience. Tapping on the screen displays overlays, this gesture is not received by the application. See also: [SystemUiChangeCallback], used to listen and respond to the change in system overlays."/>
<itemvalue="lean Back"/>
<itemvalue="Prefetches an image into the image cache. Returns a [Future] that will complete when the first image yielded by the [ImageProvider] is available or failed to load. If the image is later used by an [Image] or [BoxDecoration] or [FadeInImage], it will probably be loaded faster. The consumer of the image does not need to use the same [ImageProvider] instance. The [ImageCache] will find the image as long as both images share the same key, and the image is held by the cache. The cache may refuse to hold the image if it is disabled, the image is too large, or some other criteria implemented by a custom [ImageCache] implementation. The [ImageCache] holds a reference to all images passed to [ImageCache.putIfAbsent] as long as their [ImageStreamCompleter] has at least one listener. This method will wait until the end of the frame after its future completes before releasing its own listener. This gives callers a chance to listen to the stream if necessary. A caller can determine if the image ended up in the cache by calling [ImageProvider.obtainCacheStatus]. If it is only held as [ImageCacheStatus.live], and the caller wishes to keep the resolved image in memory, the caller should immediately call `provider.resolve` and add a listener to the returned [ImageStream]. The image will remain pinned in memory at least until the caller removes its listener from the stream, even if it would not otherwise fit into the cache. Callers should be cautious about pinning large images or a large number of images in memory, as this can result in running out of memory and being killed by the operating system. The lower the available physical memory, the more susceptible callers will be to running into OOM issues. These issues manifest as immediate process death, sometimes with no other error messages. The [BuildContext] and [Size] are used to select an image configuration (see [createLocalImageConfiguration]). The returned future will not complete with error, even if precaching failed. The `onError` argument can be used to manually handle errors while pre-caching. See also: [ImageCache], which holds images that may be reused."/>
<itemvalue="Creates a random number generator. The optional parameter [seed] is used to initialize the internal state of the generator. The implementation of the random stream can change between releases of the library."/>
<itemvalue="Creates a random number generator. The optional parameter [seed] is used to initialize the internal state of the generator. The implementation of the random stream can change between releases of the library."/>
<itemvalue="Creates a cryptographically secure random number generator. If the program cannot provide a cryptographically secure source of random numbers, it throws an [UnsupportedError]."/>
<itemvalue="Creates a cryptographically secure random number generator. If the program cannot provide a cryptographically secure source of random numbers, it throws an [UnsupportedError]."/>
<itemvalue="Makes this Rx looks like a function so you can update a new value using `rx(someOtherValue)`. Practical to assign the Rx directly to some Widget that has a signature ::onChange( value ) Example: ``` final myText = 'GetX rocks!'.obs; in your Constructor, just to check it works :P ever( myText, print ) ; in your build(BuildContext) { TextField( onChanged: myText, ), ```"/>
<itemvalue="Makes this Rx looks like a function so you can update a new value using `rx(someOtherValue)`. Practical to assign the Rx directly to some Widget that has a signature ::onChange( value ) Example: ``` final myText = 'GetX rocks!'.obs; in your Constructor, just to check it works :P ever( myText, print ) ; in your build(BuildContext) { TextField( onChanged: myText, ), ```"/>
@ -33,41 +56,19 @@
<itemvalue="Position the control on the trailing edge, and the secondary widget, if any, on the leading edge."/>
<itemvalue="Position the control on the trailing edge, and the secondary widget, if any, on the leading edge."/>
<itemvalue="Position the control on the leading edge, and the secondary widget, if any, on the trailing edge."/>
<itemvalue="Position the control on the leading edge, and the secondary widget, if any, on the trailing edge."/>
<itemvalue="Typically used to force the expansion arrow icon to the tile's leading or trailing edge. By default, the value of `controlAffinity` is [ListTileControlAffinity.platform], which means that the expansion arrow icon will appear on the tile's trailing edge."/>
<itemvalue="Typically used to force the expansion arrow icon to the tile's leading or trailing edge. By default, the value of `controlAffinity` is [ListTileControlAffinity.platform], which means that the expansion arrow icon will appear on the tile's trailing edge."/>
<itemvalue="A single-line [ListTile] with an expansion arrow icon that expands or collapses the tile to reveal or hide the [children]. This widget is typically used with [ListView] to create an "expand collapse" list entry. When used with scrolling widgets like [ListView], a unique [PageStorageKey] must be specified to enable the [ExpansionTile] to save and restore its expanded state when it is scrolled in and out of view. This class overrides the [ListTileThemeData.iconColor] and [ListTileThemeData.textColor] theme properties for its [ListTile]. These colors animate between values when the tile is expanded and collapsed: between [iconColor], [collapsedIconColor] and between [textColor] and [collapsedTextColor]. The expansion arrow icon is shown on the right by default in left-to-right languages (i.e. the trailing edge). This can be changed using [controlAffinity]. This maps to the [leading] and [trailing] properties of [ExpansionTile]. {@tool dartpad} This example demonstrates different configurations of ExpansionTile. See code in examplesapilibmaterialexpansion_tileexpansion_tile.0.dart {@end-tool} See also: [ListTile], useful for creating expansion tile [children] when the expansion tile represents a sublist. The "Expand and collapse" section of <https:material.iocomponentsliststypes>"/>
<itemvalue="show Sraft Not Saved Confirm"/>
<itemvalue="_layout Changeable Rich Text"/>
<itemvalue="可改变的"/>
<itemvalue="可变的"/>
<itemvalue="is Icon In Left"/>
<itemvalue="is Icon On Left"/>
<itemvalue="icon On Left"/>
<itemvalue="Local Key"/>
<itemvalue="A sliver that contains a single box widget. Slivers are special-purpose widgets that can be combined using a [CustomScrollView] to create custom scroll effects. A [SliverToBoxAdapter] is a basic sliver that creates a bridge back to one of the usual box-based widgets. Rather than using multiple [SliverToBoxAdapter] widgets to display multiple box widgets in a [CustomScrollView], consider using [SliverList], [SliverFixedExtentList], [SliverPrototypeExtentList], or [SliverGrid], which are more efficient because they instantiate only those children that are actually visible through the scroll view's viewport."/>
<itemvalue="A material design app bar that integrates with a [CustomScrollView]. An app bar consists of a toolbar and potentially other widgets, such as a [TabBar] and a [FlexibleSpaceBar]. App bars typically expose one or more common actions with [IconButton]s which are optionally followed by a [PopupMenuButton] for less common operations. {@youtube 560 315 https:www.youtube.comwatch?v=R9C5KMJKluE} Sliver app bars are typically used as the first child of a [CustomScrollView], which lets the app bar integrate with the scroll view so that it can vary in height according to the scroll offset or float above the other content in the scroll view. For a fixed-height app bar at the top of the screen see [AppBar], which is used in the [Scaffold.appBar] slot. The AppBar displays the toolbar widgets, [leading], [title], and [actions], above the [bottom] (if any). If a [flexibleSpace] widget is specified then it is stacked behind the toolbar and the bottom widget."/>
<itemvalue="A sliver that places multiple box children in a two dimensional arrangement. [SliverGrid] places its children in arbitrary positions determined by [gridDelegate]. Each child is forced to have the size specified by the [gridDelegate]. The main axis direction of a grid is the direction in which it scrolls; the cross axis direction is the orthogonal direction. {@youtube 560 315 https:www.youtube.comwatch?v=ORiTTaVY6mM} {@tool snippet} This example, which would be inserted into a [CustomScrollView.slivers] list, shows twenty boxes in a pretty teal grid:"/>
<itemvalue="A sliver that places multiple box children in a linear array along the main axis. Each child is forced to have the [SliverConstraints.crossAxisExtent] in the cross axis but determines its own main axis extent. [SliverList] determines its scroll offset by "dead reckoning" because children outside the visible part of the sliver are not materialized, which means [SliverList] cannot learn their main axis extent. Instead, newly materialized children are placed adjacent to existing children. {@youtube 560 315 https:www.youtube.comwatch?v=ORiTTaVY6mM} If the children have a fixed extent in the main axis, consider using [SliverFixedExtentList] rather than [SliverList] because [SliverFixedExtentList] does not need to perform layout on its children to obtain their extent in the main axis and is therefore more efficient. {@macro flutter.widgets.SliverChildDelegate.lifecycle} See also: <https:flutter.devdocsdevelopmentuiadvancedslivers>, a description of what slivers are and how to use them. [SliverFixedExtentList], which is more efficient for children with the same extent in the main axis. [SliverPrototypeExtentList], which is similar to [SliverFixedExtentList] except that it uses a prototype list item instead of a pixel value to define the main axis extent of each item. [SliverGrid], which places its children in arbitrary positions."/>
<itemvalue="A [ScrollView] that creates custom scroll effects using slivers. A [CustomScrollView] lets you supply [slivers] directly to create various scrolling effects, such as lists, grids, and expanding headers. For example, to create a scroll view that contains an expanding app bar followed by a list and a grid, use a list of three slivers: [SliverAppBar], [SliverList], and [SliverGrid]. [Widget]s in these [slivers] must produce [RenderSliver] objects. To control the initial scroll offset of the scroll view, provide a [controller] with its [ScrollController.initialScrollOffset] property set. {@animation 400 376 https:flutter.github.ioassets-for-api-docsassetswidgetscustom_scroll_view.mp4} {@tool snippet} This sample code shows a scroll view that contains a flexible pinned app bar, a grid, and an infinite list."/>
<itemvalue="A base class for the `State` of widgets with implicit animations. [ImplicitlyAnimatedWidgetState] requires that subclasses respond to the animation themselves. If you would like `setState()` to be called automatically as the animation changes, use [AnimatedWidgetBaseState]. Properties that subclasses choose to animate are represented by [Tween] instances. Subclasses must implement the [forEachTween] method to allow [ImplicitlyAnimatedWidgetState] to iterate through the widget's fields and animate them."/>
<itemvalue="Animated version of [Align] which automatically transitions the child's position over a given duration whenever the given [alignment] changes. Here's an illustration of what this can look like, using a [curve] of [Curves.fastOutSlowIn]. {@animation 250 266 https:flutter.github.ioassets-for-api-docsassetswidgetsanimated_align.mp4} For the animation, you can choose a [curve] as well as a [duration] and the widget will automatically animate to the new target [alignment]. If you require more control over the animation (e.g. if you want to stop it mid-animation), consider using an [AlignTransition] instead, which takes a provided [Animation] as argument. While that allows you to fine-tune the animation, it also requires more development overhead as you have to manually manage the lifecycle of the underlying [AnimationController]. {@tool dartpad} The following code implements the [AnimatedAlign] widget, using a [curve] of [Curves.fastOutSlowIn]. See code in examplesapilibwidgetsimplicit_animationsanimated_align.0.dart {@end-tool} See also: [AnimatedContainer], which can transition more values at once. [AnimatedPadding], which can animate the padding instead of the alignment. [AnimatedSlide], which can animate the translation of child by a given offset relative to its size. [AnimatedPositioned], which, as a child of a [Stack], automatically transitions its child's position over a given duration whenever the given position changes."/>
<itemvalue="stage 2 and 3 done."/>
<itemvalue="Optional widget to place on the line after the input. This can be used, for example, to add some padding to the text that would otherwise be specified using [suffixText], or to add a custom widget after the input. The widget's baseline is lined up with the input baseline. Only one of [suffix] and [suffixText] can be specified. The [suffix] appears before the [suffixIcon], if both are specified. See also: [prefix], the equivalent but on the leading edge."/>
<itemvalue="smart Dashes Type"/>
<itemvalue="smart Quotes Type"/>
<itemvalue="decimal"/>
<itemvalue="The number is decimal, allowing a decimal point to provide fractional. This flag is only used for the [number] input type, otherwise `null`. Use `const TextInputType.numberWithOptions(decimal: true)` to set this."/>
<itemvalue="The number is signed, allowing a positive or negative sign at the start. This flag is only used for the [number] input type, otherwise `null`. Use `const TextInputType.numberWithOptions(signed: true)` to set this."/>
debuggerx
3 years ago