From c2c7fa81701860ecf7ae4226a78f0a279dc6931e Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@163.com>
Date: Wed, 11 Jan 2023 18:58:04 +0800
Subject: [PATCH] AI-222.4459.24.2221.9445173 <debuggerx@debuggerx-e5 Update
 yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 655354f..c7e87fa 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -88,6 +88,9 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="This entry will include the widget built by this builder in the overlay at the entry's position. To cause this builder to be called again, call [markNeedsBuild] on this overlay entry." />
+      <item value="Discards any resources used by this [OverlayEntry]. This method must be called after [remove] if the [OverlayEntry] is inserted into an [Overlay]. After this is called, the object is not in a usable state and should be discarded (calls to [addListener] will throw after the object is disposed). However, the listeners registered may not be immediately released until the widget built using this [OverlayEntry] is unmounted from the widget tree. This method should only be called by the object's owner." />
+      <item value="Remove this entry from the overlay. This should only be called once. This method removes this overlay entry from the overlay immediately. The UI will be updated in the same frame if this method is called before the overlay rebuild in this frame; otherwise, the UI will be updated in the next frame. This means that it is safe to call during builds, but also that if you do call this after the overlay rebuild, the UI will not update until the next frame (i.e. many milliseconds later)." />
       <item value="Called when a notification of the appropriate type arrives at this location in the tree. Return true to cancel the notification bubbling. Return false to allow the notification to continue to be dispatched to further ancestors. Notifications vary in terms of when they are dispatched. There are two main possibilities: dispatch between frames, and dispatch during layout. For notifications that dispatch during layout, such as those that inherit from [LayoutChangedNotification], it is too late to call [State.setState] in response to the notification (as layout is currently happening in a descendant, by definition, since notifications bubble up the tree). For widgets that depend on layout, consider a [LayoutBuilder] instead." />
       <item value="分析" />
       <item value="additional relocation overflows omitted from the output" />
@@ -124,8 +127,8 @@
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="24" />
-        <entry key="ENGLISH" value="25" />
+        <entry key="CHINESE" value="26" />
+        <entry key="ENGLISH" value="27" />
         <entry key="JAVANESE" value="1" />
       </map>
     </option>