AI-Ladybug | 2024.2.1 Patch 1 <debuggerx@debuggerx-PC Update yiiguxing.translation.xml

master
debuggerx 6 months ago
parent eed2c6957f
commit 1e8c318cb3

@ -12,6 +12,14 @@
<option name="translationDialogLocationY" value="536" /> <option name="translationDialogLocationY" value="536" />
<option name="translationDialogWidth" value="1253" /> <option name="translationDialogWidth" value="1253" />
<histories> <histories>
<item value="{@macro flutter.rendering.RenderListWheelViewport.squeeze} Defaults to `1.45` to visually mimic iOS." />
<item value="The uniform height of all children. All children will be given the [BoxConstraints] to match this exact height. Must not be null and must be positive." />
<item value="item extent" />
<item value="background color" />
<item value="off axis fraction" />
<item value="use magnifier" />
<item value="Relative ratio between this picker's height and the simulated cylinder's diameter. Smaller values creates more pronounced curvatures in the scrollable wheel. For more details, see [ListWheelScrollView.diameterRatio]. Must not be null and defaults to `1.1` to visually mimic iOS." />
<item value="diameter ratio" />
<item value="minus" /> <item value="minus" />
<item value="BRITISH" /> <item value="BRITISH" />
<item value="Called whenever the widget configuration changes. If the parent widget rebuilds and requests that this location in the tree update to display a new widget with the same [runtimeType] and [Widget.key], the framework will update the [widget] property of this [State] object to refer to the new widget and then call this method with the previous widget as an argument. Override this method to respond when the [widget] changes (e.g., to start implicit animations). The framework always calls [build] after calling [didUpdateWidget], which means any calls to [setState] in [didUpdateWidget] are redundant. {@macro flutter.widgets.State.initState} Implementations of this method should start with a call to the inherited method, as in `super.didUpdateWidget(oldWidget)`. _See the discussion at [Element.rebuild] for more information on when this method is called._" /> <item value="Called whenever the widget configuration changes. If the parent widget rebuilds and requests that this location in the tree update to display a new widget with the same [runtimeType] and [Widget.key], the framework will update the [widget] property of this [State] object to refer to the new widget and then call this method with the previous widget as an argument. Override this method to respond when the [widget] changes (e.g., to start implicit animations). The framework always calls [build] after calling [didUpdateWidget], which means any calls to [setState] in [didUpdateWidget] are redundant. {@macro flutter.widgets.State.initState} Implementations of this method should start with a call to the inherited method, as in `super.didUpdateWidget(oldWidget)`. _See the discussion at [Element.rebuild] for more information on when this method is called._" />
@ -54,20 +62,12 @@
<item value="Instances of classes that either themselves are marked with `@pragma('vm:isolate-unsendable')`, extend or implement such classes cannot be sent through the ports. Apart from those exceptions any object can be sent. Objects that are identified as immutable (e.g. strings) will be shared whereas all other objects will be copied. The send happens immediately and may have a linear time cost to copy the transitive object graph. The send itself doesn't block (i.e. doesn't wait until the receiver has received the message). The corresponding receive port can receive the message as soon as its isolate's event loop is ready to deliver it, independently of what the sending isolate is doing. Note: Due to an implementation choice the Dart VM made for how closures represent captured state, closures can currently capture more state than they need, which can cause the transitive closure to be larger than needed. Open bug to address this: http:dartbug.com36983" /> <item value="Instances of classes that either themselves are marked with `@pragma('vm:isolate-unsendable')`, extend or implement such classes cannot be sent through the ports. Apart from those exceptions any object can be sent. Objects that are identified as immutable (e.g. strings) will be shared whereas all other objects will be copied. The send happens immediately and may have a linear time cost to copy the transitive object graph. The send itself doesn't block (i.e. doesn't wait until the receiver has received the message). The corresponding receive port can receive the message as soon as its isolate's event loop is ready to deliver it, independently of what the sending isolate is doing. Note: Due to an implementation choice the Dart VM made for how closures represent captured state, closures can currently capture more state than they need, which can cause the transitive closure to be larger than needed. Open bug to address this: http:dartbug.com36983" />
<item value="Illegal argument in isolate message: object is unsendable - Library:'dart:async' Class: _AsyncCompleter@4048458 (see restrictions listed at `SendPort.send()` documentation for more information)" /> <item value="Illegal argument in isolate message: object is unsendable - Library:'dart:async' Class: _AsyncCompleter@4048458 (see restrictions listed at `SendPort.send()` documentation for more information)" />
<item value="Sends an asynchronous [message] through this send port, to its corresponding [ReceivePort]. If the sending and receiving isolates do not share the same code (an isolate created using [Isolate.spawnUri] does not share the code of the isolate that spawned it), the transitive object graph of [message] can only contain the following kinds of objects: - `null` - `true` and `false` - Instances of [int], [double], [String] - Instances created through list, map and set literals - Instances created by constructors of: - [List], [Map], [LinkedHashMap], [Set] and [LinkedHashSet] - [TransferableTypedData] - [Capability] - [SendPort] instances from [ReceivePort.sendPort] or [RawReceivePort.sendPort] where the receive ports are created using those classes' constructors. - Instances of [Type] representing one of the types mentioned above, `Object`, `dynamic`, `void` and `Never` as well as nullable variants of all these types. For generic types type arguments must be sendable types for the whole type to be sendable." /> <item value="Sends an asynchronous [message] through this send port, to its corresponding [ReceivePort]. If the sending and receiving isolates do not share the same code (an isolate created using [Isolate.spawnUri] does not share the code of the isolate that spawned it), the transitive object graph of [message] can only contain the following kinds of objects: - `null` - `true` and `false` - Instances of [int], [double], [String] - Instances created through list, map and set literals - Instances created by constructors of: - [List], [Map], [LinkedHashMap], [Set] and [LinkedHashSet] - [TransferableTypedData] - [Capability] - [SendPort] instances from [ReceivePort.sendPort] or [RawReceivePort.sendPort] where the receive ports are created using those classes' constructors. - Instances of [Type] representing one of the types mentioned above, `Object`, `dynamic`, `void` and `Never` as well as nullable variants of all these types. For generic types type arguments must be sendable types for the whole type to be sendable." />
<item value="See [SendPort.send] for more information about exceptions as well as a note of warning about sending closures, which can capture more state than needed." />
<item value="The `callback`, the `message` given to it as well as the result have to be objects that can be sent across isolates (as they may be transitively copied if needed). The majority of objects can be sent across isolates." />
<item value="On web platforms this will run [callback] on the current eventloop. On native platforms this will run [callback] in a separate isolate. {@template flutter.foundation.compute.callback}" />
<item value="{@youtube 560 315 https:www.youtube.comwatch?v=5AxWC49ZMzs} {@tool snippet} The following code uses the [compute] function to check whether a given integer is a prime number." />
<item value="Asynchronously runs the given [callback] - with the provided [message] - in the background and completes with the result. {@template flutter.foundation.compute.usecase} This is useful for operations that take longer than a few milliseconds, and which would therefore risk skipping frames. For tasks that will only take a few milliseconds, consider [SchedulerBinding.scheduleTask] instead. {@endtemplate}" />
<item value="{@template flutter.material.dataTable.columnSpacing} The horizontal margin between the contents of each data column. {@endtemplate} If null, [DataTableThemeData.columnSpacing] is used. This value defaults to 56.0 to adhere to the Material Design specifications." />
<item value="{@template flutter.material.dataTable.dividerThickness} The width of the divider that appears between [TableRow]s. Must be greater than or equal to zero. {@endtemplate} If null, [DataTableThemeData.dividerThickness] is used. This value defaults to 1.0." />
<item value="Defines the horizontal layout of the [label] and sort indicator in the heading row. If [headingRowAlignment] value is [MainAxisAlignment.center] and [onSort] is not null, then a [SizedBox] with a width of sort arrow icon size and sort arrow padding will be placed before the [label] to ensure the label is centered in the column. If null, then defaults to [MainAxisAlignment.start]." />
</histories> </histories>
<option name="languageScores"> <option name="languageScores">
<map> <map>
<entry key="CHINESE" value="646" /> <entry key="CHINESE" value="646" />
<entry key="CHINESE_SIMPLIFIED" value="135" /> <entry key="CHINESE_SIMPLIFIED" value="143" />
<entry key="ENGLISH" value="777" /> <entry key="ENGLISH" value="785" />
<entry key="GERMAN" value="1" /> <entry key="GERMAN" value="1" />
<entry key="HAWAIIAN" value="1" /> <entry key="HAWAIIAN" value="1" />
<entry key="INDONESIAN" value="1" /> <entry key="INDONESIAN" value="1" />

Loading…
Cancel
Save