AndroidStudioSettings/yiiguxing.translation.xml

<application>
  <component name="Translation.Cache">
    <option name="lastTrimTime" value="1719368311091" />
  </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="The number of device pixels for each logical pixel. This number might not be a power of two. Indeed, it might not even be an integer. For example, the Nexus 6 has a device pixel ratio of 3.5." />
      <item value="Whether this range is empty (but still potentially placed inside the text)." />
      <item value="The index of the first character in the range. If [start] and [end] are both -1, the text range is empty." />
      <item value="A widget that defines a region that can detect taps inside or outside of itself and any group of regions it belongs to, without participating in the [gesture disambiguation](https:flutter.devgesturesgesture-disambiguation) system (other than to consume tap down events if [consumeOutsideTaps] is true). This widget indicates to the nearest ancestor [TapRegionSurface] that the region occupied by its child will participate in the tap detection for that surface. If this region belongs to a group (by virtue of its [groupId]), all the regions in the group will act as one. If there is no [TapRegionSurface] ancestor, [TapRegion] will do nothing." />
      <item value="A [TapRegion] that adds its children to the tap region group for widgets based on the [EditableText] text editing widget, such as [TextField] and [CupertinoTextField]. Widgets that are wrapped with a [TextFieldTapRegion] are considered to be part of a text field for purposes of unfocus behavior. So, when the user taps on them, the currently focused text field won't be unfocused by default. This allows controls like spinners, copy buttons, and formatting buttons to be associated with a text field without causing the text field to lose focus when they are interacted with. {@tool dartpad} This example shows how to use a [TextFieldTapRegion] to wrap a set of &quot;spinner&quot; buttons that increment and decrement a value in the text field without causing the text field to lose keyboard focus. This example includes a generic `SpinnerField&lt;T&gt;` class that you can copypaste into your own project and customize. See code in examplesapilibwidgetstap_regiontext_field_tap_region.0.dart {@end-tool} See also: [TapRegion], the widget that this widget uses to add widgets to the group of text fields." />
      <item value="An interface for implementing text input controls that receive text editing state changes and visual input control requests. Editing state changes and input control requests are sent by the framework when the editing state of the attached text input client changes, or it requests the input control to be shown or hidden, for example. The input control can be installed with [TextInput.setInputControl], and the default platform text input control can be restored with [TextInput.restorePlatformInputControl]. The [TextInputControl] class must be extended. [TextInputControl] implementations should call [TextInput.updateEditingValue] to send user input to the attached input client." />
      <item value="A widget that absorbs pointers during hit testing. When [absorbing] is true, this widget prevents its subtree from receiving pointer events by terminating hit testing at itself. It still consumes space during layout and paints its child as usual. It just prevents its children from being the target of located events, because it returns true from [RenderBox.hitTest]." />
      <item value="raw gesture detector" />
      <item value="A pointer device with a stylus that has been inverted." />
      <item value="A pointer device with a stylus." />
      <item value="Configuration of offset passed to [DragStartDetails]. See also: [DragGestureRecognizer.dragStartBehavior], which gives an example for the different behaviors." />
      <item value="Set the initial position at the position where this gesture recognizer won the arena." />
      <item value="{@template flutter.widgets.list_view.prototypeItem} If non-null, forces the children to have the same extent as the given widget in the scroll direction. Specifying an [prototypeItem] is more efficient than letting the children determine their own extent because the scrolling machinery can make use of the foreknowledge of the children's extent to save work, for example when the scroll position changes drastically. See also: [SliverPrototypeExtentList], the sliver used internally when this property is provided. It constrains its box children to have the same extent as a prototype item along the main axis. The [itemExtent] property, which allows forcing the children's extent to a given value. The [itemExtentBuilder] property, which allows forcing the children's extent to be the value returned by the callback. {@endtemplate}" />
      <item value="A material expansion panel. It has a header and a body and can be either expanded or collapsed. The body of the panel is only visible when it is expanded. {@youtube 560 315 https:www.youtube.comwatch?v=2aJZzRMziJc} Expansion panels are only intended to be used as children for [ExpansionPanelList]." />
      <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]." />
    </histories>
    <option name="languageScores">
      <map>
        <entry key="CHINESE" value="486" />
        <entry key="ENGLISH" value="487" />
        <entry key="HAWAIIAN" value="1" />
        <entry key="POLISH" value="1" />
        <entry key="ROMANIAN" value="1" />
      </map>
    </option>
  </component>
</application>