From a404b0a39b689de290c6fc759ba0f6e69b60bf8d Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@debuggerx-PC>
Date: Mon, 3 Jun 2024 16:48:19 +0800
Subject: [PATCH] AI-Jellyfish | 2023.3.1 Patch 1 <debuggerx@debuggerx-PC
 Update yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index c4f7d50..0d36392 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -10,6 +10,8 @@
     <option name="translationDialogLocationX" value="779" />
     <option name="translationDialogLocationY" value="568" />
     <histories>
+      <item value="Whether this entry must be included in the tree even if there is a fully [opaque] entry above it. By default, if there is an entirely [opaque] entry over this one, then this one will not be included in the widget tree (in particular, stateful widgets within the overlay entry will not be instantiated). To ensure that your overlay entry is still built even if it is not visible, set [maintainState] to true. This is more expensive, so should be done with care. In particular, if widgets in an overlay entry with [maintainState] set to true repeatedly call [State.setState], the user's battery will be drained unnecessarily. This is used by the [Navigator] and [Route] objects to ensure that routes are kept around even when in the background, so that [Future]s promised from subsequent routes will be handled properly when they complete." />
+      <item value="Whether this entry occludes the entire overlay. If an entry claims to be opaque, then, for efficiency, the overlay will skip building entries below that entry unless they have [maintainState] set." />
       <item value="Optional: pass in a controller you already have created. This is useful for testing, as you can pass in a mock instance. If no controller is passed in, one will be created automatically." />
       <item value="used for multi-languages with default layouts, the default is English only will be ignored if customLayoutKeys is not null" />
       <item value="default layouts" />
@@ -33,7 +35,6 @@
       <item value="An [Expanded] widget must be a descendant of a [Row], [Column], or [Flex], and the path from the [Expanded] widget to its enclosing [Row], [Column], or [Flex] must contain only [StatelessWidget]s or [StatefulWidget]s (not other kinds of widgets, like [RenderObjectWidget]s)." />
       <item value="Using an [Expanded] widget makes a child of a [Row], [Column], or [Flex] expand to fill the available space along the main axis (e.g., horizontally for a [Row] or vertically for a [Column]). If multiple children are expanded, the available space is divided among them according to the [flex] factor." />
       <item value="A widget that expands a child of a [Row], [Column], or [Flex] so that the child fills the available space." />
-      <item value="Whether this entry occludes the entire overlay. If an entry claims to be opaque, then, for efficiency, the overlay will skip building entries below that entry unless they have [maintainState] set." />
       <item value="opaque" />
       <item value="Creates a new repeating timer. The [callback] is invoked repeatedly with [duration] intervals until canceled with the [cancel] function. The exact timing depends on the underlying timer implementation. No more than `n` callbacks will be made in `duration n` time, but the time between two consecutive callbacks can be shorter and longer than `duration`. In particular, an implementation may schedule the next callback, e.g., a `duration` after either when the previous callback ended, when the previous callback started, or when the previous callback was scheduled for - even if the actual callback was delayed. [duration] must a non-negative [Duration]." />
       <item value="add msg" />
@@ -59,12 +60,11 @@
       <item value="The safe areas when the device is in portrait orientation." />
       <item value="The safe areas when the device is in landscape orientation." />
       <item value="strut Style" />
-      <item value="is Processing" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="449" />
-        <entry key="ENGLISH" value="450" />
+        <entry key="CHINESE" value="451" />
+        <entry key="ENGLISH" value="452" />
         <entry key="HAWAIIAN" value="1" />
         <entry key="POLISH" value="1" />
         <entry key="ROMANIAN" value="1" />