From 1e6ac56d643a1d40115f1ca8e4a986a7aae680ea Mon Sep 17 00:00:00 2001
From: dx <dx@PC-DebuggerX>
Date: Wed, 27 Mar 2024 20:03:26 +0800
Subject: [PATCH] AI-Iguana | 2023.2.1 Patch 1 <dx@PC-DebuggerX Update
 yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index d6d5793..c899763 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -7,6 +7,8 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <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]" />
       <item value="Defines the visual density of user interface components. Density, in the context of a UI, is the vertical and horizontal &quot;compactness&quot; of the components in the UI. It is unitless, since it means different things to different UI components. The default for visual densities is zero for both vertical and horizontal densities, which corresponds to the default visual density of components in the Material Design specification. It does not affect text sizes, icon sizes, or padding values. For example, for buttons, it affects the spacing around the child of the button. For lists, it affects the distance between baselines of entries in the list. For chips, it only affects the vertical size, not the horizontal size." />
@@ -55,13 +57,11 @@
       <item value="MARGIN" />
       <item value="MAX SIZE" />
       <item value="MIN SIZE" />
-      <item value="DATA MATRIX COMPACT" />
-      <item value="DATA MATRIX SHAPE" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="319" />
-        <entry key="ENGLISH" value="320" />
+        <entry key="CHINESE" value="321" />
+        <entry key="ENGLISH" value="322" />
         <entry key="HAWAIIAN" value="1" />
         <entry key="POLISH" value="1" />
         <entry key="ROMANIAN" value="1" />