AndroidStudioSettings/yiiguxing.translation.xml

<application>
  <component name="Translation.Cache">
    <option name="lastTrimTime" value="1718077261161" />
  </component>
  <component name="Translation.Settings">
    <option name="primaryLanguage" value="CHINESE" />
  </component>
  <component name="Translation.States">
    <option name="translationDialogHeight" value="702" />
    <option name="translationDialogLocationX" value="591" />
    <option name="translationDialogLocationY" value="536" />
    <option name="translationDialogWidth" value="1253" />
    <histories>
      <item value="reduced map ids" />
      <item value="初始化" />
      <item value="is ultra wide screen" />
      <item value="Fuzzy inside, nothing outside. This can make shapes appear to be lit from within." />
      <item value="Solid inside, fuzzy outside. This corresponds to drawing the shape, and additionally drawing the blur. This can make objects appear brighter, maybe even as if they were fluorescent." />
      <item value="These mirror DlBlurStyle and must be kept in sync. Fuzzy inside and outside. This is useful for painting shadows that are offset from the shape that ostensibly is casting the shadow." />
      <item value="A mask filter to apply to shapes as they are painted. A mask filter is a function that takes a bitmap of color pixels, and returns another bitmap of color pixels. Instances of this class are used with [Paint.maskFilter] on [Paint] objects." />
      <item value="A mask filter (for example, a blur) to apply to a shape after it has been drawn but before it has been composited into the image. See [MaskFilter] for details." />
      <item value="A description of the style to use when drawing on a [Canvas]. Most APIs on [Canvas] take a [Paint] object to describe the style to use for that operation." />
      <item value="The unique USB HID usage ID of this physical key on the keyboard. Due to the variations in platform APIs, this may not be the actual HID usage code from the hardware, but a value derived from available information on the platform. See &lt;https:www.usb.orgsitesdefaultfilesdocumentshut1_12v2.pdf&gt; for the HID usage values and their meanings." />
      <item value="[FocusTraversalGroup], a widget used to configure the focus traversal policy for a widget subtree." />
      <item value="[FocusTraversalPolicy], an object used to determine how to move the focus to other nodes." />
      <item value="[FocusManager], a singleton that manages the focus and distributes key events to focused nodes." />
      <item value="[FocusScopeNode], which represents a scope node in the focus hierarchy." />
      <item value="The [onKey] argument allows specification of a key event handler that is invoked when this node or one of its children has focus. Keys are handed to the primary focused widget first, and then they propagate through the ancestors of that node, stopping if one of them returns [KeyEventResult.handled] from [onKey], indicating that it has handled the event." />
      <item value="Like [Focus], [FocusScope] provides an [onFocusChange] as a way to be notified when the focus is given to or removed from this widget." />
      <item value="For example a new [FocusScope] is created automatically when a route is pushed, keeping the focus traversal from moving to a control in a previous route. If you just want to group widgets together in a group so that they are traversed in a particular order, but the focus can still leave the group, use a [FocusTraversalGroup]." />
      <item value="A [FocusScope] is similar to a [Focus], but also serves as a scope for its descendants, restricting focus traversal to the scoped controls. For example a new [FocusScope] is created automatically when a route is pushed, keeping the focus traversal from moving to a control in a previous route." />
      <item value="candidates" />
      <item value="The builder function will be called for each Key object." />
      <item value="The [Navigator] removed `route`. If only one route is being removed, then the route immediately below that one, if any, is `previousRoute`. If multiple routes are being removed, then the route below the bottommost route being removed, if any, is `previousRoute`, and this method will be called once for each removed route, from the topmost route to the bottommost route." />
      <item value="The [Navigator] popped `route`. The route immediately below that one, and thus the newly active route, is `previousRoute`." />
      <item value="The [Navigator] pushed `route`. The route immediately below that one, and thus the previously active route, is `previousRoute`." />
      <item value="Resolve debugger issue with the new Dart macro file uri format (7449) Hide deep links window when insufficient SDK version (7478) Fix exceptions out of FlutterSampleNotificationProvider (5634) Additional fixes for deprecation of ActionUpdateThread.OLD_EDT (7330) Exception from EditorPerfDecorations fixed (7432) Exception from FlutterColorProvider fixed (7428) Fix top toolbar for new UI (7423) Update JxBrowser to v7.38.2 (7413) &quot;Open Android Module in Android Studio&quot; action removed (7103) Fix for deprecation of ActionUpdateThread.OLD_EDT (7330) Deprecation of ServiceExtensions.setPubRootDirectories (7142) Fix plugin not opening in Android Studio (7305) Deadlock involving WorkspaceCache.getInstance() (7333) Fix for AlreadyDisposedException from DartVmServiceDebugProcess (7381) Memory leak fix out of DartVmServiceDebugProcess (7380) Memory leak fix in FlutterSettings and JxBrowser (7377) Delete actions specific to legacy inspector (7416)" />
      <item value="Whether this entry must be included in the tree even if there is a fully [opaque] entry above it. By default, if there is an entirely [opaque] entry over this one, then this one will not be included in the widget tree (in particular, stateful widgets within the overlay entry will not be instantiated). To ensure that your overlay entry is still built even if it is not visible, set [maintainState] to true. This is more expensive, so should be done with care. In particular, if widgets in an overlay entry with [maintainState] set to true repeatedly call [State.setState], the user's battery will be drained unnecessarily. This is used by the [Navigator] and [Route] objects to ensure that routes are kept around even when in the background, so that [Future]s promised from subsequent routes will be handled properly when they complete." />
      <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="Optional: pass in a controller you already have created. This is useful for testing, as you can pass in a mock instance. If no controller is passed in, one will be created automatically." />
      <item value="used for multi-languages with default layouts, the default is English only will be ignored if customLayoutKeys is not null" />
      <item value="default layouts" />
      <item value="extendBody locked when keyboard is open" />
      <item value="The minimum insets for contents of the Scaffold to keep visible." />
      <item value="The minimum viewPadding for interactive elements positioned by the Scaffold to keep within safe interactive areas." />
      <item value="If true the [body] and the scaffold's floating widgets should size themselves to avoid the onscreen keyboard whose height is defined by the ambient [MediaQuery]'s [MediaQueryData.viewInsets] `bottom` property. For example, if there is an onscreen keyboard displayed above the scaffold, the body can be resized to avoid overlapping the keyboard, which prevents widgets inside the body from being obscured by the keyboard. Defaults to true." />
      <item value="The number of physical pixels on each side of the display rectangle into which the view can render, but over which the operating system will likely place system UI, such as the keyboard, that fully obscures any content. When this property changes, [PlatformDispatcher.onMetricsChanged] is called. When using the Flutter framework, using [MediaQuery.of] to obtain the insets (via [MediaQueryData.viewInsets]), instead of directly obtaining the [viewInsets] from a [FlutterView], will automatically cause any widgets dependent on the insets to rebuild when they change, without having to listen to [PlatformDispatcher.onMetricsChanged]. The relationship between this [viewInsets], [viewPadding], and [padding] are described in more detail in the documentation for [FlutterView]. See also: [WidgetsBindingObserver], for a mechanism at the widgets layer to observe when this value changes. [MediaQuery.of], a simpler mechanism for the same. [Scaffold], which automatically applies the view insets in material design applications." />
      <item value="The [padding] property is computed from both [viewInsets] and [viewPadding]. It will allow a view inset to consume view padding where appropriate, such as when a phone's keyboard is covering the bottom view padding and so &quot;absorbs&quot; it. Clients that want to position elements relative to the view padding regardless of the view insets should use the [viewPadding] property, e.g. if you wish to draw a widget at the center of the screen with respect to the iPhone &quot;safe area&quot; regardless of whether the keyboard is showing. [padding] is useful for clients that want to know how much padding should be accounted for without concern for the current inset(s) state, e.g. determining whether a gesture should be considered for scrolling purposes. This value varies based on the current state of the insets. For example, a visible keyboard will consume all gestures in the bottom part of the [viewPadding] anyway, so there is no need to account for that in the [padding], which is always safe to use for such calculations." />
      <item value="The parts of the display that are completely obscured by system UI, typically by the device's keyboard. When a mobile device's keyboard is visible `viewInsets.bottom` corresponds to the top of the keyboard. This value is independent of the [padding] and [viewPadding]. viewPadding is measured from the edges of the [MediaQuery] widget's bounds. Padding is calculated based on the viewPadding and viewInsets. The bounds of the top level MediaQuery created by [WidgetsApp] are the same as the window (often the mobile device screen) that contains the app. {@youtube 560 315 https:www.youtube.comwatch?v=ceCo8U0XHqw} See also: [FlutterView], which provides some additional detail about this property and how it relates to [padding] and [viewPadding]." />
      <item value="{@template dio.CancelToken} Controls cancellation of [Dio]'s requests. The same token can be shared between different requests. When [cancel] is invoked, requests bound to this token will be cancelled. {@endtemplate}" />
      <item value="An optional maximum number of lines for the text to span, wrapping if necessary. If the text exceeds the given number of lines, it will be truncated according to [overflow]. If this is 1, text will not wrap. Otherwise, text will be wrapped at the edge of the box. If this is null, but there is an ambient [DefaultTextStyle] that specifies an explicit number for its [DefaultTextStyle.maxLines], then the [DefaultTextStyle] value will take precedence. You can use a [RichText] widget directly to entirely override the [DefaultTextStyle]." />
      <item value="Whether to show or hide a child. By default, the [visible] property controls whether the [child] is included in the subtree or not; when it is not [visible], the [replacement] child (typically a zero-sized box) is included instead. A variety of flags can be used to tweak exactly how the child is hidden. (Changing the flags dynamically is discouraged, as it can cause the [child] subtree to be rebuilt, with any state in the subtree being discarded. Typically, only the [visible] flag is changed dynamically.)" />
      <item value="An optional maximum number of lines for the text to span, wrapping if necessary. If the text exceeds the given number of lines, it will be truncated according to [overflow]. If this is 1, text will not wrap. Otherwise, text will be wrapped at the edge of the box. If this is non-null, it will override even explicit null values of [Text.maxLines]." />
      <item value="{@template dart.ui.textHeightBehavior} Defines how to apply [TextStyle.height] over and under text. [TextHeightBehavior.applyHeightToFirstAscent] and [TextHeightBehavior.applyHeightToLastDescent] represent whether the [TextStyle.height] modifier will be applied to the corresponding metric. By default both properties are true, and [TextStyle.height] is applied as normal. When set to false, the font's default ascent will be used. [TextHeightBehavior.leadingDistribution] determines how the leading is distributed over and under text. This property applies before [TextHeightBehavior.applyHeightToFirstAscent] and [TextHeightBehavior.applyHeightToLastDescent]. {@endtemplate}" />
      <item value="An unmodifiable list of the UTF-16 code units of this string." />
      <item value="Spacer creates an adjustable, empty spacer that can be used to tune the spacing between widgets in a [Flex] container, like [Row] or [Column]. The [Spacer] widget will take up any available space, so setting the [Flex.mainAxisAlignment] on a flex container that contains a [Spacer] to [MainAxisAlignment.spaceAround], [MainAxisAlignment.spaceBetween], or [MainAxisAlignment.spaceEvenly] will not have any visible effect: the [Spacer] has taken up all of the additional space, therefore there is none left to redistribute." />
      <item value="A widget that controls how a child of a [Row], [Column], or [Flex] flexes. Using a [Flexible] widget gives a child of a [Row], [Column], or [Flex] the flexibility to expand to fill the available space in the main axis (e.g., horizontally for a [Row] or vertically for a [Column]), but, unlike [Expanded], [Flexible] does not require the child to fill the available space. A [Flexible] widget must be a descendant of a [Row], [Column], or [Flex], and the path from the [Flexible] widget to its enclosing [Row], [Column], or [Flex] must contain only [StatelessWidget]s or [StatefulWidget]s (not other kinds of widgets, like [RenderObjectWidget]s)." />
      <item value="![This results in two thin blue boxes with a larger amber box in between.](https:flutter.github.ioassets-for-api-docsassetswidgetsexpanded_column.png)" />
      <item value="{@tool dartpad} This example shows how to use an [Expanded] widget in a [Column] so that its middle child, a [Container] here, expands to fill the space." />
      <item value="An [Expanded] widget must be a descendant of a [Row], [Column], or [Flex], and the path from the [Expanded] widget to its enclosing [Row], [Column], or [Flex] must contain only [StatelessWidget]s or [StatefulWidget]s (not other kinds of widgets, like [RenderObjectWidget]s)." />
      <item value="Using an [Expanded] widget makes a child of a [Row], [Column], or [Flex] expand to fill the available space along the main axis (e.g., horizontally for a [Row] or vertically for a [Column]). If multiple children are expanded, the available space is divided among them according to the [flex] factor." />
      <item value="A widget that expands a child of a [Row], [Column], or [Flex] so that the child fills the available space." />
      <item value="opaque" />
    </histories>
    <option name="languageScores">
      <map>
        <entry key="CHINESE" value="473" />
        <entry key="ENGLISH" value="474" />
        <entry key="HAWAIIAN" value="1" />
        <entry key="POLISH" value="1" />
        <entry key="ROMANIAN" value="1" />
      </map>
    </option>
  </component>
</application>