AI-Otter | 2025.2.1 <debuggerx@debuggerx-PC Update yiiguxing.translation.xml

find.xml

@@ -2,6 +2,8 @@
   <component name="FindSettings">
     <option name="customScope" value="Project Files" />
     <option name="defaultScopeName" value="Project Files" />
+    <option name="localRegularExpressions" value="true" />
+    <option name="LOCAL_REGULAR_EXPRESSIONS" value="true" />
     <option name="SEARCH_SCOPE" value="Project Files" />
     <mask>*.css</mask>
     <mask>*.html</mask>

yiiguxing.translation.xml

@@ -22,6 +22,7 @@
     <option name="translationDialogLocationY" value="567" />
     <option name="translationDialogWidth" value="1381" />
     <histories>
+      <item value="Standard output from the process. The value used for the `stdoutEncoding` argument to [Process.run] determines the type. If `null` was used, this value is of type [Uint8List] otherwise it is of type `String`." />
       <item value="A rectangle upon which a backend texture is mapped. Backend textures are images that can be applied (mapped) to an area of the Flutter view. They are created, managed, and updated using a platform-specific texture registry. This is typically done by a plugin that integrates with host platform video player, camera, or OpenGL APIs, or similar image sources. A texture widget refers to its backend texture using an integer ID. Texture IDs are obtained from the texture registry and are scoped to the Flutter view. Texture IDs may be reused after deregistration, at the discretion of the registry. The use of texture IDs currently unknown to the registry will silently result in a blank rectangle. Texture widgets are repainted autonomously as dictated by the backend (e.g. on arrival of a video frame). Such repainting generally does not involve executing Dart code. The size of the rectangle is determined by its parent widget, and the texture is automatically scaled to fit." />
       <item value="Texture" />
       <item value="Identity" />
@@ -71,7 +72,6 @@
       <item value="Set the initial position at the position where this gesture recognizer won the arena." />
       <item value="Set the initial offset at the position where the first down event was detected." />
       <item value="With this flag set to false, when accessibility focus reaches the end of the current page and the user attempts to move it to the next element, the focus will traverse to the next widget outside of the page view." />
-      <item value="Controls whether the widget's pages will respond to [RenderObject.showOnScreen], which will allow for implicit accessibility scrolling." />
     </histories>
     <option name="languageScores">
       <map>