From f192497b78cc344bc9ec0adc56ac42804013b74c Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@debuggerx-PC>
Date: Tue, 15 Oct 2024 17:18:42 +0800
Subject: [PATCH] AI-Ladybug | 2024.2.1 <debuggerx@debuggerx-PC Update
 yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 023e816..4eafe22 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -12,6 +12,7 @@
     <option name="translationDialogLocationY" value="536" />
     <option name="translationDialogWidth" value="1253" />
     <histories>
+      <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" />
@@ -61,13 +62,12 @@
       <item value="An [Iterable] of Unicode code-points of this string. If the string contains surrogate pairs, they are combined and returned as one integer by this iterator. Unmatched surrogate halves are treated like valid 16-bit code-units." />
       <item value="Whether this [State] object is currently in a tree. After creating a [State] object and before calling [initState], the framework &quot;mounts&quot; the [State] object by associating it with a [BuildContext]. The [State] object remains mounted until the framework calls [dispose], after which time the framework will never ask the [State] object to [build] again. It is an error to call [setState] unless [mounted] is true." />
       <item value="Whether the [Widget] this context is associated with is currently mounted in the widget tree. Accessing the properties of the [BuildContext] or calling any methods on it is only valid while mounted is true. If mounted is false, assertions will trigger. Once unmounted, a given [BuildContext] will never become mounted again. {@macro flutter.widgets.BuildContext.asynchronous_gap}" />
-      <item value="Unhandled Exception: This widget has been unmounted, so the State no longer has a context (and should be considered defunct). Consider canceling any active work during &quot;dispose&quot; or using the &quot;mounted&quot; getter to determine if the State is still active." />
     </histories>
     <option name="languageScores">
       <map>
         <entry key="CHINESE" value="646" />
-        <entry key="CHINESE_SIMPLIFIED" value="97" />
-        <entry key="ENGLISH" value="742" />
+        <entry key="CHINESE_SIMPLIFIED" value="98" />
+        <entry key="ENGLISH" value="743" />
         <entry key="HAWAIIAN" value="1" />
         <entry key="INDONESIAN" value="1" />
         <entry key="NORWEGIAN" value="1" />