From 58a4a7b0d10d93a55d07bf295c2e9f11e7f99e5a Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@gmail.com>
Date: Wed, 28 Sep 2022 09:55:39 +0800
Subject: [PATCH] AI-Dolphin | 2021.3.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 1cb3981..c847228 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="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); }" />
       <item value="Cause the record did not support by hive cache, remove this value by now Comment reply to record, null by default, soulsRecord or usersRecord. if reply to type is soul, this value is soul record if reply to type is user, this value is user record dynamic replyToRecord;" />
@@ -55,12 +56,11 @@
       <item value="Makes a direct update of [value] adding it to the Stream useful when you make use of Rx for custom Types to referesh your UI. Sample: ``` class Person { String name, last; int age; Person({this.name, this.last, this.age}); @override String toString() =&gt; 'name last, age years old'; } final person = Person(name: 'John', last: 'Doe', age: 18).obs; person.value.name = 'Roi'; person.refresh(); print( person ); ```" />
       <item value="change new onboarding conditions" />
       <item value="判断条件" />
-      <item value="listen details after join group chat." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="351" />
-        <entry key="ENGLISH" value="352" />
+        <entry key="CHINESE" value="353" />
+        <entry key="ENGLISH" value="354" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>