From 0c74e8ab610deee81a1fd094623f565f8339fc2a Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@163.com>
Date: Fri, 8 Apr 2022 10:33:31 +0800
Subject: [PATCH] AI-Bumblebee | 2021.1.1 Patch 2 <debuggerx@debuggerx-PC
 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 aa84baf..1a7777d 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -1,6 +1,7 @@
 <application>
   <component name="AppStorage">
     <histories>
+      <item value="Displays a Material dialog above the current contents of the app, with Material entrance and exit animations, modal barrier color, and modal barrier behavior (dialog is dismissible with a tap on the barrier). This function takes a `builder` which typically builds a [Dialog] widget. Content below the dialog is dimmed with a [ModalBarrier]. The widget returned by the `builder` does not share a context with the location that `showDialog` is originally called from. Use a [StatefulBuilder] or a custom [StatefulWidget] if the dialog needs to update dynamically. The `context` argument is used to look up the [Navigator] and [Theme] for the dialog. It is only used when the method is called. Its corresponding widget can be safely removed from the tree before the dialog is closed. The `barrierDismissible` argument is used to indicate whether tapping on the barrier will dismiss the dialog. It is `true` by default and can not be `null`. The `barrierColor` argument is used to specify the color of the modal barrier that darkens everything below the dialog. If `null` the default color `Colors.black54` is used. The `useSafeArea` argument is used to indicate if the dialog should only display in 'safe' areas of the screen not used by the operating system (see [SafeArea] for more details). It is `true` by default, which means the dialog will not overlap operating system areas. If it is set to `false` the dialog will only be constrained by the screen size. It can not be `null`. The `useRootNavigator` argument is used to determine whether to push the dialog to the [Navigator] furthest from or nearest to the given `context`. By default, `useRootNavigator` is `true` and the dialog route created by this method is pushed to the root navigator. It can not be `null`. The `routeSettings` argument is passed to [showGeneralDialog], see [RouteSettings] for details. If the application has multiple [Navigator] objects, it may be necessary to call `Navigator.of(context, rootNavigator: true).pop(result)` to close the dialog rather than just `Navigator.pop(context, result)`. Returns a [Future] that resolves to the value (if any) that was passed to [Navigator.pop] when the dialog was closed. State Restoration in Dialogs Using this method will not enable state restoration for the dialog. In order to enable state restoration for a dialog, use [Navigator.restorablePush] or [Navigator.restorablePushNamed] with [DialogRoute]. For more information about state restoration, see [RestorationManager]. {@tool sample} This sample demonstrates how to create a restorable Material dialog. This is accomplished by enabling state restoration by specifying [MaterialApp.restorationScopeId] and using [Navigator.restorablePush] to push [DialogRoute] when the button is tapped. {@macro flutter.widgets.RestorationManager} See code in examplesapilibmaterialdialogshow_dialog.0.dart {@end-tool} See also: [AlertDialog], for dialogs that have a row of buttons below a body. [SimpleDialog], which handles the scrolling of the contents and does not show buttons below its body. [Dialog], on which [SimpleDialog] and [AlertDialog] are based. [showCupertinoDialog], which displays an iOS-style dialog. [showGeneralDialog], which allows for customization of the dialog popup. &lt;https:material.iodesigncomponentsdialogs.html&gt;" />
       <item value="The day of the week [monday]..[sunday]. In accordance with ISO 8601 a week starts with Monday, which has the value 1. ```dart final moonLanding = DateTime.parse('1969-07-20 20:18:04Z'); print(moonLanding.weekday); 7 assert(moonLanding.weekday == DateTime.sunday);" />
       <item value="联系人" />
       <item value="时间戳" />
@@ -9,8 +10,8 @@
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="3" />
-        <entry key="ENGLISH" value="4" />
+        <entry key="CHINESE" value="4" />
+        <entry key="ENGLISH" value="5" />
       </map>
     </option>
   </component>