AI-Chipmunk | 2021.2.1 Patch 2 <debuggerx@debuggerx Update yiiguxing.translation.xml

master
debuggerx 3 years ago
parent de17ddbdc2
commit 6ab569d67c

@ -6,6 +6,8 @@
<option name="newTranslationDialogY" value="447" /> <option name="newTranslationDialogY" value="447" />
<option name="pinTranslationDialog" value="true" /> <option name="pinTranslationDialog" value="true" />
<histories> <histories>
<item value="A scrolling container that animates items when they are inserted or removed. This widget's [AnimatedListState] can be used to dynamically insert or remove items. To refer to the [AnimatedListState] either provide a [GlobalKey] or use the static [of] method from an item's input callback. This widget is similar to one created by [ListView.builder]. {@youtube 560 315 https:www.youtube.comwatch?v=ZtfItHwFlZ8} {@tool dartpad} This sample application uses an [AnimatedList] to create an effect when items are removed or added to the list. See code in examplesapilibwidgetsanimated_listanimated_list.0.dart {@end-tool} See also: [SliverAnimatedList], a sliver that animates items when they are inserted or removed from a list." />
<item value="{@template flutter.widgets.animatedList.initialItemCount} The number of items the list will start with. The appearance of the initial items is not animated. They are created, as needed, by [itemBuilder] with an animation parameter of [kAlwaysCompleteAnimation]. {@endtemplate}" />
<item value="Insert the given entry into the overlay. If `below` is non-null, the entry is inserted just below `below`. If `above` is non-null, the entry is inserted just above `above`. Otherwise, the entry is inserted on top. It is an error to specify both `above` and `below`." /> <item value="Insert the given entry into the overlay. If `below` is non-null, the entry is inserted just below `below`. If `above` is non-null, the entry is inserted just above `above`. Otherwise, the entry is inserted on top. It is an error to specify both `above` and `below`." />
<item value="Obs: unlike other get methods, this one you need to send a function that returns the widget to the page argument, like this: Get.offUntil(GetPageRoute(page: () =&gt; HomePage()), predicate)" /> <item value="Obs: unlike other get methods, this one you need to send a function that returns the widget to the page argument, like this: Get.offUntil(GetPageRoute(page: () =&gt; HomePage()), predicate)" />
<item value="confetti Controller" /> <item value="confetti Controller" />
@ -54,13 +56,11 @@
<item value="create Main User Record" /> <item value="create Main User Record" />
<item value="A mixin class for providing string and [DiagnosticsNode] debug representations describing the properties of an object. The string debug representation is generated from the intermediate [DiagnosticsNode] representation. The [DiagnosticsNode] representation is also used by debugging tools displaying interactive trees of objects and properties. See also: [debugFillProperties], which lists best practices for specifying the properties of a [DiagnosticsNode]. The most common use case is to override [debugFillProperties] defining custom properties for a subclass of [DiagnosticableTreeMixin] using the existing [DiagnosticsProperty] subclasses. [DiagnosticableTree], which extends this class to also describe the children of a tree structured object. [DiagnosticableTree.debugDescribeChildren], which lists best practices for describing the children of a [DiagnosticsNode]. Typically the base class already describes the children of a node properly or a node has no children. [DiagnosticsProperty], which should be used to create leaf diagnostic nodes without properties or children. There are many [DiagnosticsProperty] subclasses to handle common use cases." /> <item value="A mixin class for providing string and [DiagnosticsNode] debug representations describing the properties of an object. The string debug representation is generated from the intermediate [DiagnosticsNode] representation. The [DiagnosticsNode] representation is also used by debugging tools displaying interactive trees of objects and properties. See also: [debugFillProperties], which lists best practices for specifying the properties of a [DiagnosticsNode]. The most common use case is to override [debugFillProperties] defining custom properties for a subclass of [DiagnosticableTreeMixin] using the existing [DiagnosticsProperty] subclasses. [DiagnosticableTree], which extends this class to also describe the children of a tree structured object. [DiagnosticableTree.debugDescribeChildren], which lists best practices for describing the children of a [DiagnosticsNode]. Typically the base class already describes the children of a node properly or a node has no children. [DiagnosticsProperty], which should be used to create leaf diagnostic nodes without properties or children. There are many [DiagnosticsProperty] subclasses to handle common use cases." />
<item value="Finds [Semantics] widgets matching the given `label`, either by [RegExp.hasMatch] or string equality. The framework may combine semantics labels in certain scenarios, such as when multiple [Text] widgets are in a [MaterialButton] widget. In such a case, it may be preferable to match by regular expression. Consumers of this API __must not__ introduce unsuitable content into the semantics tree for the purposes of testing; in particular, you should prefer matching by regular expression rather than by string if the framework has combined your semantics, and not try to force the framework to break up the semantics nodes. Breaking up the nodes would have an undesirable effect on screen readers and other accessibility services. Sample code ```dart expect(find.bySemanticsLabel('Back'), findsOneWidget); ``` If the `skipOffstage` argument is true (the default), then this skips nodes that are [Offstage] or that are from inactive [Route]s." /> <item value="Finds [Semantics] widgets matching the given `label`, either by [RegExp.hasMatch] or string equality. The framework may combine semantics labels in certain scenarios, such as when multiple [Text] widgets are in a [MaterialButton] widget. In such a case, it may be preferable to match by regular expression. Consumers of this API __must not__ introduce unsuitable content into the semantics tree for the purposes of testing; in particular, you should prefer matching by regular expression rather than by string if the framework has combined your semantics, and not try to force the framework to break up the semantics nodes. Breaking up the nodes would have an undesirable effect on screen readers and other accessibility services. Sample code ```dart expect(find.bySemanticsLabel('Back'), findsOneWidget); ``` If the `skipOffstage` argument is true (the default), then this skips nodes that are [Offstage] or that are from inactive [Route]s." />
<item value="Cached &amp; lazily loaded instance of [FirebasePlatform]. Avoids a [MethodChannelFirebase] being initialized until the user starts using Firebase. The property is visible for testing to allow tests to set a mock instance directly as a static property since the class is not initialized." />
<item value="优化" />
</histories> </histories>
<option name="languageScores"> <option name="languageScores">
<map> <map>
<entry key="CHINESE" value="326" /> <entry key="CHINESE" value="329" />
<entry key="ENGLISH" value="327" /> <entry key="ENGLISH" value="330" />
<entry key="GERMAN" value="1" /> <entry key="GERMAN" value="1" />
<entry key="FRENCH" value="1" /> <entry key="FRENCH" value="1" />
</map> </map>

Loading…
Cancel
Save