AI-Chipmunk | 2021.2.1 Patch 2 <debuggerx@debuggerx Update yiiguxing.translation.xml

debugger.xml

@@ -113,9 +113,7 @@
   </component>
   <component name="XDebuggerSettings">
     <data-views />
-    <general>
+    <general />
-      <evaluation-dialog-mode>CODE_FRAGMENT</evaluation-dialog-mode>
-    </general>
     <debuggers>
       <debugger id="ObjectiveC">
         <configuration>

yiiguxing.translation.xml

@@ -6,6 +6,20 @@
     <option name="newTranslationDialogY" value="447" />
     <option name="pinTranslationDialog" value="true" />
     <histories>
+      <item value="Sign Up Referral Page" />
+      <item value="Indicates a document within the query was removed (either deleted or no longer matches the query." />
+      <item value="Indicates a document within the query was modified." />
+      <item value="Indicates a new document was added to the set of documents matching the query." />
+      <item value="used for [SmartRefresh.onLoading] since snapshot will automatically receive latest changes there is no need for [SmartRefresh.onRefresh] [onLoading] will expand the [limitSize] so that a resubscription is needed [onLimitChange] will perform all necessary operations and tell us whether if pagination has reached the end." />
+      <item value="Warning: A call to tap() with finder &quot;exactly one widget with text &quot;Delete&quot; (ignoring offstage widgets): Text(&quot;Delete&quot;, inherit: true, family: Montserrat_600, familyFallback: [Montserrat], size: 18.0, weight: 600, letterSpacing: -0.2, height: 1.2x, dependencies: [MediaQuery, DefaultTextStyle])&quot; derived an Offset (Offset(98.0, 1028.0)) that would not hit test on the specified widget. Maybe the widget is actually off-screen, or another widget is obscuring it, or the widget cannot receive pointer events. Indeed, Offset(98.0, 1028.0) is outside the bounds of the root of the render tree, Size(375.0, 812.0). The finder corresponds to this RenderBox: RenderParagrapha74b7 relayoutBoundary=up20 The hit test result at that offset is: HitTestResult(HitTestEntrycc50d(RenderView113c1), HitTestEntry8b8b2(&lt;AutomatedTestWidgetsFlutterBinding&gt;))" />
+      <item value="To silence this warning, pass &quot;warnIfMissed: false&quot; to &quot;tap()&quot;. To make this warning fatal, set WidgetController.hitTestWarningShouldBeFatal to true." />
+      <item value="Warning: A call to tap() with finder &quot;exactly one widget with text &quot;Delete&quot; (ignoring offstage widgets): Text(&quot;Delete&quot;, inherit: true, family: Montserrat_600, familyFallback: [Montserrat], size: 18.0, weight: 600, letterSpacing: -0.2, height: 1.2x, dependencies: [MediaQuery, DefaultTextStyle])&quot; derived an Offset (Offset(98.0, 1028.0)) that would not hit test on the specified widget. Maybe the widget is actually off-screen, or another widget is obscuring it, or the widget cannot receive pointer events. Indeed, Offset(98.0, 1028.0) is outside the bounds of the root of the render tree, Size(375.0, 812.0). The finder corresponds to this RenderBox: RenderParagraphcc8a4 relayoutBoundary=up20 The hit test result at that offset is: HitTestResult(HitTestEntryc7125(RenderView6eff7), HitTestEntryeb0ec(&lt;AutomatedTestWidgetsFlutterBinding&gt;))" />
+      <item value="The overflowing RenderFlex has an orientation of Axis.horizontal. The edge of the RenderFlex that is overflowing has been marked in the rendering with a yellow and black striped pattern. This is usually caused by the contents being too big for the RenderFlex. Consider applying a flex factor (e.g. using an Expanded widget) to force the children of the RenderFlex to fit within the available space instead of being sized to their natural size. This is considered an error condition because it indicates that there is content that cannot be seen. If the content is legitimately bigger than the available space, consider clipping it with a ClipRect widget before putting it in the flex, or using a scrollable container rather than a Flex, like a ListView." />
+      <item value="Warning: A call to tap() with finder &quot;exactly one widget with text &quot;Delete&quot; (ignoring offstage widgets): Text(&quot;Delete&quot;, inherit: true, family: Montserrat_600, familyFallback: [Montserrat], size: 38.4, weight: 600, letterSpacing: -0.2, height: 1.2x, dependencies: [MediaQuery, DefaultTextStyle])&quot; derived an Offset (Offset(209.6, 1060.8)) that would not hit test on the specified widget. Maybe the widget is actually off-screen, or another widget is obscuring it, or the widget cannot receive pointer events. Indeed, Offset(209.6, 1060.8) is outside the bounds of the root of the render tree, Size(800.0, 600.0)." />
+      <item value="Warning: At least one test in this suite creates an HttpClient. When running a test suite that uses TestWidgetsFlutterBinding, all HTTP requests will return status code 400, and no network request will actually be made. Any test expecting a real network connection and status code will fail. To test code that needs an HttpClient, provide your own HttpClient implementation to the code under test, so that your test can consistently provide a testable response to the code under test." />
+      <item value="create Main User Record" />
+      <item value="A mixin class for providing string and [DiagnosticsNode] debug representations describing the properties of an object. The string debug representation is generated from the intermediate [DiagnosticsNode] representation. The [DiagnosticsNode] representation is also used by debugging tools displaying interactive trees of objects and properties. See also: [debugFillProperties], which lists best practices for specifying the properties of a [DiagnosticsNode]. The most common use case is to override [debugFillProperties] defining custom properties for a subclass of [DiagnosticableTreeMixin] using the existing [DiagnosticsProperty] subclasses. [DiagnosticableTree], which extends this class to also describe the children of a tree structured object. [DiagnosticableTree.debugDescribeChildren], which lists best practices for describing the children of a [DiagnosticsNode]. Typically the base class already describes the children of a node properly or a node has no children. [DiagnosticsProperty], which should be used to create leaf diagnostic nodes without properties or children. There are many [DiagnosticsProperty] subclasses to handle common use cases." />
+      <item value="Finds [Semantics] widgets matching the given `label`, either by [RegExp.hasMatch] or string equality. The framework may combine semantics labels in certain scenarios, such as when multiple [Text] widgets are in a [MaterialButton] widget. In such a case, it may be preferable to match by regular expression. Consumers of this API __must not__ introduce unsuitable content into the semantics tree for the purposes of testing; in particular, you should prefer matching by regular expression rather than by string if the framework has combined your semantics, and not try to force the framework to break up the semantics nodes. Breaking up the nodes would have an undesirable effect on screen readers and other accessibility services. Sample code ```dart expect(find.bySemanticsLabel('Back'), findsOneWidget); ``` If the `skipOffstage` argument is true (the default), then this skips nodes that are [Offstage] or that are from inactive [Route]s." />
       <item value="Cached &amp; lazily loaded instance of [FirebasePlatform]. Avoids a [MethodChannelFirebase] being initialized until the user starts using Firebase. The property is visible for testing to allow tests to set a mock instance directly as a static property since the class is not initialized." />
       <item value="优化" />
       <item value="数量" />
@@ -42,25 +56,11 @@
       <item value="compaction Strategy" />
       <item value="time After Framework Init Micros" />
       <item value="time To First Frame Micros" />
-      <item value="time To First Frame Rasterized Micros" />
-      <item value="time To Framework Init Micros" />
-      <item value="engine Enter Timestamp Micros" />
-      <item value="is on waitlist" />
-      <item value="problem" />
-      <item value="tag" />
-      <item value="problem tag" />
-      <item value="feat: GS-1026 update report." />
-      <item value="Submission" />
-      <item value="fix: do not occlude delete button." />
-      <item value="遮挡" />
-      <item value="ratio" />
-      <item value="A [Slidable] notification that can bubble up the widget tree. You can determine the type of a notification using the `is` operator to check the [runtimeType] of the notification. To listen for notifications in a subtree, use a [SlidableNotificationListener]. To send a notification, call [dispatch] on the notification you wish to send. The notification will be delivered to the closest [SlidableNotificationListener] widget." />
-      <item value="Called when a notification of the appropriate arrives at this location in the tree." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="273" />
+        <entry key="CHINESE" value="288" />
-        <entry key="ENGLISH" value="274" />
+        <entry key="ENGLISH" value="289" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>