From 8d6a8fbb86edde6714d598a951b8e34d432136db Mon Sep 17 00:00:00 2001
From: debuggerx <debuggerx@debuggerx-PC>
Date: Sat, 20 Apr 2024 10:08:32 +0800
Subject: [PATCH] AI-Iguana | 2023.2.1 Patch 2 <debuggerx@debuggerx-PC Update
 yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 527b766..6df5216 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -7,6 +7,7 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="Ideal for short audio files, since it reduces the impacts on visuals or UI performance. In this mode the backend won't fire any duration, position or playback completion events. This means you are responsible for stopping the player. Also, it is not possible to use the seek method to set the audio to a specific position." />
       <item value="Creates a formatter that only allows characters matching a pattern." />
       <item value="Text Input Formatter" />
       <item value="Whether the [InputDecorator.child] is part of a dense form (i.e., uses less vertical space). Defaults to false." />
@@ -56,7 +57,6 @@
       <item value="The number of device pixels for each logical pixel for the screen this view is displayed on. This number might not be a power of two. Indeed, it might not even be an integer. For example, the Nexus 6 has a device pixel ratio of 3.5. Device pixels are also referred to as physical pixels. Logical pixels are also referred to as device-independent or resolution-independent pixels. By definition, there are roughly 38 logical pixels per centimeter, or about 96 logical pixels per inch, of the physical display. The value returned by [devicePixelRatio] is ultimately obtained either from the hardware itself, the device drivers, or a hard-coded value stored in the operating system or firmware, and may be inaccurate, sometimes by a significant margin. The Flutter framework operates in logical pixels, so it is rarely necessary to directly deal with this property. When this changes, [PlatformDispatcher.onMetricsChanged] is called. When using the Flutter framework, using [MediaQuery.of] to obtain the device pixel ratio (via [MediaQueryData.devicePixelRatio]), instead of directly obtaining the [devicePixelRatio] from a [FlutterView], will automatically cause any widgets dependent on this value to rebuild when it changes, without having to listen to [PlatformDispatcher.onMetricsChanged]. See also: [WidgetsBindingObserver], for a mechanism at the widgets layer to observe when this value changes. [Display.devicePixelRatio], which reports the DPR of the display. The value here is equal to the value exposed on [display]." />
       <item value="Subsequent version, remove this deprecated member. ignore: deprecated_member_use" />
       <item value="Dynamically loads the |EnableNonClientDpiScaling| from the User32 module. This API is only needed for PerMonitor V1 awareness mode." />
-      <item value="[ThemeData.visualDensity], where this property is used to specify the base horizontal density of Material components. [Material design guidance on density]" />
     </histories>
     <option name="languageScores">
       <map>