From 6e4ed50dee8b210c3b0e325e96eb086d937297a2 Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@163.com>
Date: Mon, 5 Dec 2022 19:12:36 +0800
Subject: [PATCH] AI-222.4345.14.2221.9321504 <debuggerx@debuggerx-e5 Update
 yiiguxing.translation.xml

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

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 3ecd03f..600b55d 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -88,14 +88,15 @@
   </component>
   <component name="Translation.States">
     <histories>
+      <item value="Explanation" />
       <item value="A [Notification] related to scrolling. [Scrollable] widgets notify their ancestors about scrolling-related changes. The notifications have the following lifecycle: A [ScrollStartNotification], which indicates that the widget has started scrolling. Zero or more [ScrollUpdateNotification]s, which indicate that the widget has changed its scroll position, mixed with zero or more [OverscrollNotification]s, which indicate that the widget has not changed its scroll position because the change would have caused its scroll position to go outside its scroll bounds. Interspersed with the [ScrollUpdateNotification]s and [OverscrollNotification]s are zero or more [UserScrollNotification]s, which indicate that the user has changed the direction in which they are scrolling. A [ScrollEndNotification], which indicates that the widget has stopped scrolling. A [UserScrollNotification], with a [UserScrollNotification.direction] of [ScrollDirection.idle]. Notifications bubble up through the tree, which means a given [NotificationListener] will receive notifications for all descendant [Scrollable] widgets. To focus on notifications from the nearest [Scrollable] descendant, check that the [depth] property of the notification is zero. When a scroll notification is received by a [NotificationListener], the listener will have already completed build and layout, and it is therefore too late for that widget to call [State.setState]. Any attempt to adjust the build or layout based on a scroll notification would result in a layout that lagged one frame behind, which is a poor user experience. Scroll notifications are therefore primarily useful for paint effects (since paint happens after layout). The [GlowingOverscrollIndicator] and [Scrollbar] widgets are examples of paint effects that use scroll notifications. To drive layout based on the scroll position, consider listening to the [ScrollPosition] directly (or indirectly via a [ScrollController])." />
       <item value="post Init State" />
       <item value="medium" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="1" />
-        <entry key="ENGLISH" value="2" />
+        <entry key="CHINESE" value="2" />
+        <entry key="ENGLISH" value="3" />
       </map>
     </option>
   </component>