From bf82eb8e56dc52427e6f865b541e34b063dd605e Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@debuggerx-PC>
Date: Mon, 9 Jun 2025 11:58:25 +0800
Subject: [PATCH] AI-Meerkat Feature Drop | 2024.3.2 Patch 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 0debe11..9ea517f 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -1,6 +1,6 @@
 <application>
   <component name="Translation.Cache">
-    <option name="lastTrimTime" value="1749005605037" />
+    <option name="lastTrimTime" value="1749440837925" />
   </component>
   <component name="Translation.OpenAISettings">
     <option name="OPEN_AI">
@@ -18,6 +18,8 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="In debug mode, if [debugTracePostFrameCallbacks] is set to true, then the registered callback will show up in the timeline events chart, which can be viewed in [DevTools](https:docs.flutter.devtoolsdevtools). In that case, the `debugLabel` argument specifies the name of the callback as it will appear in the timeline. In profile and release builds, post-frame are never traced, and the `debugLabel` argument is ignored." />
+      <item value="Schedule a callback for the end of this frame. The provided callback is run immediately after a frame, just after the persistent frame callbacks (which is when the main rendering pipeline has been flushed). This method does not request a new frame. If a frame is already in progress and the execution of post-frame callbacks has not yet begun, then the registered callback is executed at the end of the current frame. Otherwise, the registered callback is executed after the next frame (whenever that may be, if ever). The callbacks are executed in the order in which they have been added." />
       <item value="These physics cause the carousel item to snap to item boundaries." />
       <item value="Scroll physics used by a [CarouselView]." />
       <item value="Scroll physics that always lets the user scroll." />
@@ -66,8 +68,6 @@
       <item value="Creates information for editing a run of text. The selection and composing range must be within the text. This is not checked during construction, and must be guaranteed by the caller. The default value of [selection] is `TextSelection.collapsed(offset: -1)`. This indicates that there is no selection at all." />
       <item value="The offset at which the selection terminates. When the user uses the arrow keys to adjust the selection, this is the value that changes. Similarly, if the current theme paints a caret on one side of the selection, this is the location at which to paint the caret. Might be larger than, smaller than, or equal to base." />
       <item value="The offset at which the selection originates. Might be larger than, smaller than, or equal to extent." />
-      <item value="!newValue.composing.isValid || newValue.isComposingRangeValid, 'New TextEditingValue newValue has an invalid non-empty composing range ' '{newValue.composing}. It is recommended to use a valid composing range, ' 'even for readonly text fields.'," />
-      <item value="Updates the current [text] to the given `newText`, and removes existing selection and composing range held by the controller. This setter is typically only used in tests, as it resets the cursor position and the composing state. For production code, consider using the [value] setter to update the [text] value instead, and specify a reasonable selection range within the new [text]. Setting this notifies all the listeners of this [TextEditingController] that they need to update (it calls [notifyListeners]). For this reason, this value should only be set between frames, e.g. in response to user actions, not during the build, layout, or paint phases. This property can be set from a listener added to this [TextEditingController]." />
     </histories>
     <option name="languageScores">
       <map>