From 70513d4a1d9df2427eaa3b1640aa1a267122ecf9 Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@debuggerx-PC>
Date: Thu, 17 Apr 2025 18:23:46 +0800
Subject: [PATCH] AI-Meerkat | 2024.3.1 Patch 1 <debuggerx@debuggerx-PC Update
 yiiguxing.translation.xml

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

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index e2f24eb..0a149e8 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -18,6 +18,11 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="If true: on desktop platforms, a drag handle is stacked over the center of each item's trailing edge; on mobile platforms, a long press anywhere on the item starts a drag. The default desktop drag handle is just an [Icons.drag_handle] wrapped by a [ReorderableDragStartListener]. On mobile platforms, the entire item is wrapped with a [ReorderableDelayedDragStartListener]. To change the appearance or the layout of the drag handles, make this parameter false and wrap each list item, or a widget within each list item, with [ReorderableDragStartListener] or [ReorderableDelayedDragStartListener], or a custom subclass of [ReorderableDragStartListener]. The following sample specifies `buildDefaultDragHandles: false`, and uses a [Card] at the leading edge of each item for the item's drag handle. {@tool dartpad} See code in examplesapilibmaterialreorderable_listreorderable_list_view.build_default_drag_handles.0.dart {@end-tool}" />
+      <item value="{@macro flutter.widgets.list_view.prototypeItem} final Widget? prototypeItem;" />
+      <item value="This example demonstrates using the [ReorderableListView.proxyDecorator] callback to customize the appearance of a list item while it's being dragged." />
+      <item value="By default, on [TargetPlatformVariant.desktop] platforms each item will have a drag handle added on top of it that will allow the user to grab it to move the item. On [TargetPlatformVariant.mobile], no drag handle will be added, but when the user long presses anywhere on the item it will start moving the item. Displaying drag handles can be controlled with [ReorderableListView.buildDefaultDragHandles]." />
+      <item value="A list whose items the user can interactively reorder by dragging. {@youtube 560 315 https:www.youtube.comwatch?v=3fB1mxOsqJE} This sample shows by dragging the user can reorder the items of the list. The [onReorder] parameter is required and will be called when a child widget is dragged to a new position." />
       <item value="move toolbox to side navigator." />
       <item value="emotion id" />
       <item value="If [allowImplicitScrolling] is true, the [PageView] will participate in accessibility scrolling more like a [ListView], where implicit scroll actions will move to the next page rather than into the contents of the [PageView]." />
@@ -63,11 +68,6 @@
       <item value="Draws a shadow for a [Path] representing the given material elevation. The `transparentOccluder` argument should be true if the occluding object is not opaque. The arguments must not be null." />
       <item value="A pointer that has triggered a long-press with a primary button has stopped contacting the screen." />
       <item value="A pointer that has triggered a long-press with a primary button has stopped contacting the screen. This is equivalent to (and is called immediately after) [onLongPressEnd]. The only difference between the two is that this callback does not contain details of the state of the pointer when it stopped contacting the screen." />
-      <item value="Frequency of calling [listener] from the moment the stick is dragged, by default 100 milliseconds." />
-      <item value="AM control panel view model" />
-      <item value="AM control pannel view model" />
-      <item value="Arabic" />
-      <item value="If true, tells the focus traversal policy to skip over this node for purposes of the traversal algorithm. This may be used to place nodes in the focus tree that may be focused, but not traversed, allowing them to receive key events as part of the focus chain, but not be traversed to via focus traversal. This is different from [canRequestFocus] because it only implies that the node can't be reached via traversal, not that it can't be focused. It may still be focused explicitly." />
     </histories>
     <option name="languageScores">
       <map>