AI-Meerkat Feature Drop | 2024.3.2 Patch 1 <debuggerx@debuggerx-PC Update find.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

@@ -18,6 +18,13 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="The amount the pointer has moved along the primary axis in the coordinate space of the event receiver since the previous update. If the [GestureDragUpdateCallback] is for a one-dimensional drag (e.g., a horizontal or vertical drag), then this value contains the component of [delta] along the primary axis (e.g., horizontal or vertical, respectively). Otherwise, if the [GestureDragUpdateCallback] is for a two-dimensional drag (e.g., a pan), then this value is null. Defaults to null if not specified in the constructor." />
+      <item value="The local position in the coordinate system of the event receiver at which the pointer contacted the screen. Defaults to [globalPosition] if not specified in the constructor." />
+      <item value="The pointer's global position when it triggered this update. See also: [localPosition], which is the [globalPosition] transformed to the coordinate space of the event receiver." />
+      <item value="The amount the pointer has moved in the coordinate space of the event receiver since the previous update. If the [GestureDragUpdateCallback] is for a one-dimensional drag (e.g., a horizontal or vertical drag), then this offset contains only the delta in that direction (i.e., the coordinate in the other direction is zero). Defaults to zero if not specified in the constructor." />
+      <item value="Details object for callbacks that use [GestureDragUpdateCallback]." />
+      <item value="options changable" />
+      <item value="track" />
       <item value="too short" />
       <item value="Translucent targets both receive events within their bounds and permit targets visually behind them to also receive events." />
       <item value="Opaque targets can be hit by hit tests, causing them to both receive events within their bounds and prevent targets visually behind them from also receiving events." />
@@ -61,13 +68,6 @@
       <item value="Scroll physics that attempt to keep the scroll position in range when the contents change dimensions suddenly." />
       <item value="Scroll physics for environments that prevent the scroll offset from reaching beyond the bounds of the content." />
       <item value="Reduces a collection to a single value by iteratively combining each element of the collection with an existing value" />
-      <item value="Returns a new color with the provided components updated. Each component ([alpha], [red], [green], [blue]) represents a floating-point value; see [Color.from] for details and examples. If [colorSpace] is provided, and is different than the current color space, the component values are updated before transforming them to the provided [ColorSpace]. Example: ```dart import 'dart:ui'; Create a color with 50% opacity. Color makeTransparent(Color color) =&gt; color.withValues(alpha: 0.5);" />
-      <item value="Returns a new color that matches this color with the alpha channel replaced with `a` (which ranges from 0 to 255). Out of range values will have unexpected effects." />
-      <item value="Returns a new color that matches this color with the alpha channel replaced with the given `opacity` (which ranges from 0.0 to 1.0). Out of range values will have unexpected effects." />
-      <item value="Column is also a layout widget. It takes a list of children and arranges them vertically. By default, it sizes itself to fit its children horizontally, and tries to be as tall as its parent. Column has various properties to control how it sizes itself and how it positions its children. Here we use mainAxisAlignment to center the children vertically; the main axis here is the vertical axis because Columns are vertical (the cross axis would be horizontal). TRY THIS: Invoke &quot;debug painting&quot; (choose the &quot;Toggle Debug Paint&quot; action in the IDE, or press &quot;p&quot;" />
-      <item value="Represents the interactive &quot;state&quot; of this widget in terms of a set of [WidgetState]s, including [WidgetState.disabled], [WidgetState.hovered], [WidgetState.error], and [WidgetState.focused]. Classes based on this one can provide their own [WidgetStatesController] to which they've added listeners. They can also update the controller's [WidgetStatesController.value] however, this may only be done when it's safe to call [State.setState], like in an event handler. The controller's [WidgetStatesController.value] represents the set of states that a widget's visual properties, typically [WidgetStateProperty] values, are resolved against. It is _not_ the intrinsic state of the widget. The widget is responsible for ensuring that the controller's [WidgetStatesController.value] tracks its intrinsic state. For example one cannot request the keyboard focus for a widget by adding [WidgetState.focused] to its controller. When the widget gains the or loses the focus it will [WidgetStatesController.update] its controller's [WidgetStatesController.value] and notify listeners of the change." />
-      <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. Post-frame callbacks cannot be unregistered. They are called exactly once. 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="音量" />
     </histories>
     <option name="languageScores">
       <map>