From e492fb9a1d7c0960b8d4c4add5adcf328e20d18b Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@gmail.com>
Date: Thu, 20 Oct 2022 14:23:55 +0800
Subject: [PATCH] AI-Dolphin | 2021.3.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 73e1883..a8063f2 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -6,6 +6,7 @@
     <option name="newTranslationDialogY" value="447" />
     <option name="pinTranslationDialog" value="true" />
     <histories>
+      <item value="Local Key" />
       <item value="A sliver that contains a single box widget. Slivers are special-purpose widgets that can be combined using a [CustomScrollView] to create custom scroll effects. A [SliverToBoxAdapter] is a basic sliver that creates a bridge back to one of the usual box-based widgets. Rather than using multiple [SliverToBoxAdapter] widgets to display multiple box widgets in a [CustomScrollView], consider using [SliverList], [SliverFixedExtentList], [SliverPrototypeExtentList], or [SliverGrid], which are more efficient because they instantiate only those children that are actually visible through the scroll view's viewport." />
       <item value="A material design app bar that integrates with a [CustomScrollView]. An app bar consists of a toolbar and potentially other widgets, such as a [TabBar] and a [FlexibleSpaceBar]. App bars typically expose one or more common actions with [IconButton]s which are optionally followed by a [PopupMenuButton] for less common operations. {@youtube 560 315 https:www.youtube.comwatch?v=R9C5KMJKluE} Sliver app bars are typically used as the first child of a [CustomScrollView], which lets the app bar integrate with the scroll view so that it can vary in height according to the scroll offset or float above the other content in the scroll view. For a fixed-height app bar at the top of the screen see [AppBar], which is used in the [Scaffold.appBar] slot. The AppBar displays the toolbar widgets, [leading], [title], and [actions], above the [bottom] (if any). If a [flexibleSpace] widget is specified then it is stacked behind the toolbar and the bottom widget." />
       <item value="A sliver that places multiple box children in a two dimensional arrangement. [SliverGrid] places its children in arbitrary positions determined by [gridDelegate]. Each child is forced to have the size specified by the [gridDelegate]. The main axis direction of a grid is the direction in which it scrolls; the cross axis direction is the orthogonal direction. {@youtube 560 315 https:www.youtube.comwatch?v=ORiTTaVY6mM} {@tool snippet} This example, which would be inserted into a [CustomScrollView.slivers] list, shows twenty boxes in a pretty teal grid:" />
@@ -55,12 +56,11 @@
       <item value="Initializes a new [FirebaseApp] instance by [name] and [options] and returns the created app. This method should be called before any usage of FlutterFire plugins. The default app instance can be initialized here simply by passing no &quot;name&quot; as an argument in both Dart &amp; manual initialization flows." />
       <item value="Notify the framework that the internal state of this object has changed. Whenever you change the internal state of a [State] object, make the change in a function that you pass to [setState]: ```dart setState(() { _myState = newValue; }); ``` The provided callback is immediately called synchronously. It must not return a future (the callback cannot be `async`), since then it would be unclear when the state was actually being set. Calling [setState] notifies the framework that the internal state of this object has changed in a way that might impact the user interface in this subtree, which causes the framework to schedule a [build] for this [State] object. If you just change the state directly without calling [setState], the framework might not schedule a [build] and the user interface for this subtree might not be updated to reflect the new state. Generally it is recommended that the `setState` method only be used to wrap the actual changes to the state, not any computation that might be associated with the change. For example, here a value used by the [build] function is incremented, and then the change is written to disk, but only the increment is wrapped in the `setState`: ```dart Future&lt;void&gt; _incrementCounter() async { setState(() { _counter++; }); Directory directory = await getApplicationDocumentsDirectory(); final String dirName = directory.path; await File('dircounter.txt').writeAsString('_counter'); } ``` It is an error to call this method after the framework calls [dispose]. You can determine whether it is legal to call this method by checking whether the [mounted] property is true." />
       <item value="Makes this Rx looks like a function so you can update a new value using `rx(someOtherValue)`. Practical to assign the Rx directly to some Widget that has a signature ::onChange( value ) Example: ``` final myText = 'GetX rocks!'.obs; in your Constructor, just to check it works :P ever( myText, print ) ; in your build(BuildContext) { TextField( onChanged: myText, )," />
-      <item value="updates the value to `null` and adds it to the Stream. Even with null-safety coming, is still an important feature to support, as `call()` doesn't accept `null` values. For instance, `InputDecoration.errorText` has to be null to not show the &quot;error state&quot;. Sample: ``` final inputError = ''.obs..nil(); print('{inputError.runtimeType}: inputError'); outputs &gt; RxString: null ``` void nil() { subject.add(_value = null); }" />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="406" />
-        <entry key="ENGLISH" value="407" />
+        <entry key="CHINESE" value="408" />
+        <entry key="ENGLISH" value="409" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>