You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
84 lines
17 KiB
84 lines
17 KiB
<application>
|
|
<component name="AppStorage">
|
|
<option name="newTranslationDialogHeight" value="304" />
|
|
<option name="newTranslationDialogWidth" value="406" />
|
|
<option name="newTranslationDialogX" value="811" />
|
|
<option name="newTranslationDialogY" value="447" />
|
|
<option name="pinTranslationDialog" value="true" />
|
|
<histories>
|
|
<item value="maintain State" />
|
|
<item value="opaque" />
|
|
<item value="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." />
|
|
<item value="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." />
|
|
<item value="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." />
|
|
<item value="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]." />
|
|
<item value="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." />
|
|
<item value="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." />
|
|
<item value="lean Back" />
|
|
<item value="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." />
|
|
<item value="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." />
|
|
<item value="Creates a cryptographically secure random number generator. If the program cannot provide a cryptographically secure source of random numbers, it throws an [UnsupportedError]." />
|
|
<item value="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, ), ```" />
|
|
<item value="'Widgets that mix AutomaticKeepAliveClientMixin into their State must ' 'call super.build() but must ignore the return value of the superclass.'," />
|
|
<item value="Called when this object is removed from the tree permanently. The framework calls this method when this [State] object will never build again. After the framework calls [dispose], the [State] object is considered unmounted and the [mounted] property is false. It is an error to call [setState] at this point. This stage of the lifecycle is terminal: there is no way to remount a [State] object that has been disposed. Subclasses should override this method to release any resources retained by this object (e.g., stop any active animations). {@macro flutter.widgets.State.initState} Implementations of this method should end with a call to the inherited method, as in `super.dispose()`. See also: [deactivate], which is called prior to [dispose]." />
|
|
<item value="audit Toxic" />
|
|
<item value="BuiltList can not be serialization." />
|
|
<item value="序列化" />
|
|
<item value="create Item" />
|
|
<item value="transaction" />
|
|
<item value="group Chat Ref" />
|
|
<item value="check Name Exist" />
|
|
<item value="update Soul Avatar" />
|
|
<item value="已修复" />
|
|
<item value="FIXED" />
|
|
<item value="decline" />
|
|
<item value="gamification" />
|
|
<item value="sealed" />
|
|
<item value="A [DocumentReference] refers to a document location in a [FirebaseFirestore] database and can be used to write, read, or listen to the location. The document at the referenced location may or may not exist. A [DocumentReference] can also be used to create a [CollectionReference] to a subcollection." />
|
|
<item value="is Lol" />
|
|
<item value="is Rant" />
|
|
<item value="is Comfort" />
|
|
<item value="If true the [body] and the scaffold's floating widgets should size themselves to avoid the onscreen keyboard whose height is defined by the ambient [MediaQuery]'s [MediaQueryData.viewInsets] `bottom` property. For example, if there is an onscreen keyboard displayed above the scaffold, the body can be resized to avoid overlapping the keyboard, which prevents widgets inside the body from being obscured by the keyboard. Defaults to true." />
|
|
<item value="Position the control relative to the text in the fashion that is typical for the current platform, and place the secondary widget on the opposite side." />
|
|
<item value="Position the control on the trailing edge, and the secondary widget, if any, on the leading edge." />
|
|
<item value="Position the control on the leading edge, and the secondary widget, if any, on the trailing edge." />
|
|
<item value="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." />
|
|
<item value="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>" />
|
|
<item value="show Sraft Not Saved Confirm" />
|
|
<item value="_layout Changeable Rich Text" />
|
|
<item value="可改变的" />
|
|
<item value="可变的" />
|
|
<item value="is Icon In Left" />
|
|
<item value="is Icon On Left" />
|
|
<item value="icon On Left" />
|
|
<item value="Local Key" />
|
|
<item value="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." />
|
|
<item value="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." />
|
|
<item value="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:" />
|
|
<item value="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." />
|
|
</histories>
|
|
<option name="languageScores">
|
|
<map>
|
|
<entry key="CHINESE" value="454" />
|
|
<entry key="ENGLISH" value="455" />
|
|
<entry key="GERMAN" value="1" />
|
|
<entry key="FRENCH" value="1" />
|
|
</map>
|
|
</option>
|
|
</component>
|
|
<component name="Cache">
|
|
<option name="lastTrimTime" value="1667801591460" />
|
|
</component>
|
|
<component name="Settings">
|
|
<option name="phoneticFontFamily" value="DejaVu Sans Mono" />
|
|
<option name="primaryFontFamily" value="Noto Sans CJK SC Regular" />
|
|
<option name="showActionsInContextMenuOnlyWithSelection" value="false" />
|
|
<option name="translateDocumentation" value="true" />
|
|
<option name="translator" value="YOUDAO" />
|
|
<option name="youdaoTranslateSettings">
|
|
<youdao-translate>
|
|
<option name="appId" value="6ff353d64c7c642b" />
|
|
</youdao-translate>
|
|
</option>
|
|
</component>
|
|
</application> |