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

master
DebuggerX 3 years ago
parent 448c8e07ad
commit ac6f1324e7

@ -4,6 +4,7 @@
<option name="newTranslationDialogX" value="811" />
<option name="newTranslationDialogY" value="447" />
<histories>
<item value="Describes how [Scrollable] widgets should behave. {@template flutter.widgets.scrollBehavior} Used by [ScrollConfiguration] to configure the [Scrollable] widgets in a subtree. This class can be extended to further customize a [ScrollBehavior] for a subtree. For example, overriding [ScrollBehavior.getScrollPhysics] sets the default [ScrollPhysics] for [Scrollable]s that inherit this [ScrollConfiguration]. Overriding [ScrollBehavior.buildOverscrollIndicator] can be used to add or change the default [GlowingOverscrollIndicator] decoration, while [ScrollBehavior.buildScrollbar] can be changed to modify the default [Scrollbar]. When looking to easily toggle the default decorations, you can use [ScrollBehavior.copyWith] instead of creating your own [ScrollBehavior] class. The `scrollbar` and `overscrollIndicator` flags can turn these decorations off. {@endtemplate} See also: [ScrollConfiguration], the inherited widget that controls how [Scrollable] widgets behave in a subtree. @immutable" />
<item value="allow Implicit Scrolling" />
<item value="should Accept User Offset" />
<item value="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." />
@ -53,12 +54,11 @@
<item value="avoid refreshData when user deleted." />
<item value="update default avatar assets." />
<item value="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(&quot;vm:recognized&quot;, &quot;other&quot;)" />
<item value="Add delay before hide skeletons." />
</histories>
<option name="languageScores">
<map>
<entry key="CHINESE" value="132" />
<entry key="ENGLISH" value="133" />
<entry key="CHINESE" value="133" />
<entry key="ENGLISH" value="134" />
</map>
</option>
</component>

Loading…
Cancel
Save