From e0eaef723cda597bc39357ee8e387f6ec975368a Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@gmail.com>
Date: Thu, 28 Jul 2022 16:55:00 +0800
Subject: [PATCH] AI-Chipmunk | 2021.2.1 Patch 1 <debuggerx@debuggerx Update
 yiiguxing.translation.xml

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

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index bf93380..af871e8 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -5,6 +5,7 @@
     <option name="newTranslationDialogX" value="811" />
     <option name="newTranslationDialogY" value="447" />
     <histories>
+      <item value="Linearly interpolate between two colors. This is intended to be fast but as a result may be ugly. Consider [HSVColor] or writing custom logic for interpolating colors. If either color is null, this function linearly interpolates from a transparent instance of the other color. This is usually preferable to interpolating from [material.Colors.transparent] (`const Color(0x00000000)`), which is specifically transparent _black_. The `t` argument represents position on the timeline, with 0.0 meaning that the interpolation has not started, returning `a` (or something equivalent to `a`), 1.0 meaning that the interpolation has finished, returning `b` (or something equivalent to `b`), and values in between meaning that the interpolation is at the relevant point on the timeline between `a` and `b`. The interpolation can be extrapolated beyond 0.0 and 1.0, so negative values and values greater than 1.0 are valid (and can easily be generated by curves such as [Curves.elasticInOut]). Each channel will be clamped to the range 0 to 255. Values for `t` are usually obtained from an [Animation&lt;double&gt;], such as an [AnimationController]." />
       <item value="open Profile Card" />
       <item value="_state" />
       <item value="Navigation.pushReplacement() shortcut .&lt;br&gt;&lt;br&gt; Pop the current page and pushes a new `page` to the stack It has the advantage of not needing context, so you can call from your business logic You can set a custom [transition], define a Tween [curve], and a transition [duration]. You can send any type of value to the other route in the [arguments]. Just like native routing in Flutter, you can push a route as a [fullscreenDialog], [id] is for when you are using nested navigation, as explained in documentation If you want the same behavior of ios that pops a route when the user drag, you can set [popGesture] to true If you're using the [Bindings] api, you must define it here By default, GetX will prevent you from push a route that you already in, if you want to push anyway, set [preventDuplicates] to false" />
@@ -54,12 +55,11 @@
       <item value="Never Scrollable Scroll Physics" />
       <item value="Bouncing Scroll Physics" />
       <item value="Determines the overscroll by applying the boundary conditions. Called by [ScrollPosition.applyBoundaryConditions], which is called by [ScrollPosition.setPixels] just before the [ScrollPosition.pixels] value is updated, to determine how much of the offset is to be clamped off and sent to [ScrollPosition.didOverscrollBy]. The `value` argument is guaranteed to not equal the [ScrollMetrics.pixels] of the `position` argument when this is called. It is possible for this method to be called when the `position` describes an already-out-of-bounds position. In that case, the boundary conditions should usually only prevent a further increase in the extent to which the position is out of bounds, allowing a decrease to be applied successfully, so that (for instance) an animation can smoothly snap an out of bounds position to the bounds. See [BallisticScrollActivity]. This method must not clamp parts of the offset that are entirely within the bounds described by the given `position`. The given `position` is only valid during this method call. Do not keep a reference to it to use later, as the values may update, may not update, or may update to reflect an entirely unrelated scrollable. Examples [BouncingScrollPhysics] returns zero. In other words, it allows scrolling past the boundary unhindered. [ClampingScrollPhysics] returns the amount by which the value is beyond the position or the boundary, whichever is furthest from the content. In other words, it disallows scrolling past the boundary, but allows scrolling back from being overscrolled, if for some reason the position ends up overscrolled." />
-      <item value="Update the scroll position ([pixels]) to a given pixel value. This should only be called by the current [ScrollActivity], either during the transient callback phase or in response to user input. Returns the overscroll, if any. If the return value is 0.0, that means that [pixels] now returns the given `value`. If the return value is positive, then [pixels] is less than the requested `value` by the given amount (overscroll past the max extent), and if it is negative, it is greater than the requested `value` by the given amount (underscroll past the min extent). The amount of overscroll is computed by [applyBoundaryConditions]. The amount of the change that is applied is reported using [didUpdateScrollPositionBy]. If there is any overscroll, it is reported using [didOverscrollBy]." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="177" />
-        <entry key="ENGLISH" value="178" />
+        <entry key="CHINESE" value="178" />
+        <entry key="ENGLISH" value="179" />
         <entry key="FRENCH" value="1" />
       </map>
     </option>