AI-Meerkat Feature Drop | 2024.3.2 Patch 1 <debuggerx@debuggerx-PC Update yiiguxing.translation.xml

yiiguxing.translation.xml

@@ -18,6 +18,7 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <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." />
       <item value="Targets that defer to their children receive events within their bounds only if one of their children is hit by the hit test." />
@@ -67,7 +68,6 @@
       <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="音量" />
-      <item value="volume" />
     </histories>
     <option name="languageScores">
       <map>