From 7a92f08ea4f623cd6af0d9078345611acde1dcd5 Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@debuggerx-PC>
Date: Sat, 2 Nov 2024 16:35:10 +0800
Subject: [PATCH] AI-Ladybug | 2024.2.1 Patch 1 <debuggerx@debuggerx-PC Update
 yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 36 ++++++++++++++++++------------------
 1 file changed, 18 insertions(+), 18 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 46f591f..43d4ae4 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -12,14 +12,27 @@
     <option name="translationDialogLocationY" value="536" />
     <option name="translationDialogWidth" value="1253" />
     <histories>
+      <item value="magnification" />
+      <item value="use magnifier" />
+      <item value="off axis fraction" />
+      <item value="perspective" />
+      <item value="diameter ratio" />
+      <item value="physics" />
+      <item value="controller" />
+      <item value="A delegate that supplies children for [ListWheelScrollView] using a builder callback. [ListWheelScrollView] lazily constructs its children to avoid creating more children than are visible through the [Viewport]. This delegate provides children using an [IndexedWidgetBuilder] callback, so that the children do not have to be built until they are displayed." />
+      <item value="list wheel child builder delegate" />
+      <item value="list wheel child looping list delegate" />
+      <item value="list wheel child list delegate" />
+      <item value="Constructs a list in which children are scrolled a wheel. Its children are managed by a delegate and are lazily built during layout." />
+      <item value="A box in which children on a wheel can be scrolled. This widget is similar to a [ListView] but with the restriction that all children must be the same size along the scrolling axis. {@youtube 560 315 https:www.youtube.comwatch?v=dUhmWAz4C7Y} When the list is at the zero scroll offset, the first child is aligned with the middle of the viewport. When the list is at the final scroll offset, the last child is aligned with the middle of the viewport. The children are rendered as if rotating on a wheel instead of scrolling on a plane." />
+      <item value="over and under center opacity" />
+      <item value="this.controller, this.physics, this.diameterRatio = RenderListWheelViewport.defaultDiameterRatio, this.perspective = RenderListWheelViewport.defaultPerspective, this.offAxisFraction = 0.0, this.useMagnifier = false, this.magnification = 1.0, this.overAndUnderCenterOpacity = 1.0, required this.itemExtent, this.squeeze = 1.0, this.onSelectedItemChanged, this.renderChildrenOutsideViewport = false, this.clipBehavior = Clip.hardEdge, this.restorationId, this.scrollBehavior," />
+      <item value="An arbitrary but aesthetically reasonable default value for [perspective]." />
       <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="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._" />
@@ -49,25 +62,12 @@
       <item value="single attachment" />
       <item value="UNSPECIFIED" />
       <item value="cur subtask name" />
-      <item value="锚点" />
-      <item value="[end], if provided, must be greater than or equal to [start]." />
-      <item value="is single quoted" />
-      <item value="visit string interpolation" />
-      <item value="visit interpolation string" />
-      <item value="duplicate" />
-      <item value="重复" />
-      <item value="It will return the SheetObject of `sheet`. If the `sheet` does not exist then it will create `sheet` with `New Sheet Object`" />
-      <item value="- `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="If the sender and receiver isolate share the same code (e.g. isolates created via [Isolate.spawn]), the transitive object graph of [message] can contain any object, with the following exceptions:" />
-      <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="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." />
     </histories>
     <option name="languageScores">
       <map>
         <entry key="CHINESE" value="646" />
-        <entry key="CHINESE_SIMPLIFIED" value="143" />
-        <entry key="ENGLISH" value="785" />
+        <entry key="CHINESE_SIMPLIFIED" value="164" />
+        <entry key="ENGLISH" value="806" />
         <entry key="GERMAN" value="1" />
         <entry key="HAWAIIAN" value="1" />
         <entry key="INDONESIAN" value="1" />