From f6fc16dc2909e175f0e85b18f527ba7adcf336b7 Mon Sep 17 00:00:00 2001
From: debuggerx <dx8917312@163.com>
Date: Mon, 7 Nov 2022 18:43:59 +0800
Subject: [PATCH] AI-222.4345.14.2221.9228443 <debuggerx@debuggerx-e5 Update
 yiiguxing.translation.xml

---
 yiiguxing.translation.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/yiiguxing.translation.xml b/yiiguxing.translation.xml
index 07e7489..bd49635 100644
--- a/yiiguxing.translation.xml
+++ b/yiiguxing.translation.xml
@@ -6,6 +6,9 @@
     <option name="newTranslationDialogY" value="447" />
     <option name="pinTranslationDialog" value="true" />
     <histories>
+      <item value="Whether this entry occludes the entire overlay. If an entry claims to be opaque, then, for efficiency, the overlay will skip building entries below that entry unless they have [maintainState] set." />
+      <item value="_status Bar Hidded" />
+      <item value="_status Bar Hidden" />
       <item value="maintain State" />
       <item value="opaque" />
       <item value="Schedule a callback for the end of this frame. Does not request a new frame. This callback is run during a frame, just after the persistent frame callbacks (which is when the main rendering pipeline has been flushed). If a frame is in progress and post-frame callbacks haven't been executed yet, then the registered callback is still executed during the frame. Otherwise, the registered callback is executed during the next frame. The callbacks are executed in the order in which they have been added. Post-frame callbacks cannot be unregistered. They are called exactly once. See also: [scheduleFrameCallback], which registers a callback for the start of the next frame." />
@@ -53,14 +56,11 @@
       <item value="icon On Left" />
       <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:" />
-      <item value="A sliver that places multiple box children in a linear array along the main axis. Each child is forced to have the [SliverConstraints.crossAxisExtent] in the cross axis but determines its own main axis extent. [SliverList] determines its scroll offset by &quot;dead reckoning&quot; because children outside the visible part of the sliver are not materialized, which means [SliverList] cannot learn their main axis extent. Instead, newly materialized children are placed adjacent to existing children. {@youtube 560 315 https:www.youtube.comwatch?v=ORiTTaVY6mM} If the children have a fixed extent in the main axis, consider using [SliverFixedExtentList] rather than [SliverList] because [SliverFixedExtentList] does not need to perform layout on its children to obtain their extent in the main axis and is therefore more efficient. {@macro flutter.widgets.SliverChildDelegate.lifecycle} See also: &lt;https:flutter.devdocsdevelopmentuiadvancedslivers&gt;, a description of what slivers are and how to use them. [SliverFixedExtentList], which is more efficient for children with the same extent in the main axis. [SliverPrototypeExtentList], which is similar to [SliverFixedExtentList] except that it uses a prototype list item instead of a pixel value to define the main axis extent of each item. [SliverGrid], which places its children in arbitrary positions." />
     </histories>
     <option name="languageScores">
       <map>
-        <entry key="CHINESE" value="454" />
-        <entry key="ENGLISH" value="455" />
+        <entry key="CHINESE" value="457" />
+        <entry key="ENGLISH" value="458" />
         <entry key="GERMAN" value="1" />
         <entry key="FRENCH" value="1" />
       </map>