You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
33 lines
7.0 KiB
33 lines
7.0 KiB
<application>
|
|
<component name="Translation.Cache">
|
|
<option name="lastTrimTime" value="1676881093543" />
|
|
</component>
|
|
<component name="Translation.States">
|
|
<histories>
|
|
<item value="Specifies the [SystemUiMode] to have visible when the application is running. The `overlays` argument is a list of [SystemUiOverlay] enum values denoting the overlays to show when configured with [SystemUiMode.manual]. If a particular mode is unsupported on the platform, enabling or disabling that mode will be ignored. The settings here can be overridden by the platform when System UI becomes necessary for functionality. For example, on Android, when the keyboard becomes visible, it will enable the navigation bar and status bar system UI overlays. When the keyboard is closed, Android will not restore the previous UI visibility settings, and the UI visibility cannot be changed until 1 second after the keyboard is closed to prevent malware locking users from navigation buttons. To regain "fullscreen" after text entry, the UI overlays can be set again after a delay of at least 1 second through [restoreSystemUIOverlays] or calling this again. Otherwise, the original UI overlay settings will be automatically restored only when the application loses and regains focus. Alternatively, a [SystemUiChangeCallback] can be provided to respond to changes in the System UI. This will be called, for example, when in [SystemUiMode.leanBack] and the user taps the screen to bring up the system overlays. The callback provides a boolean to represent if the application is currently in a fullscreen mode or not, so that the application can respond to these changes. When `systemOverlaysAreVisible` is true, the application is not fullscreen. See [SystemChrome.setSystemUIChangeCallback] to respond to these changes in a fullscreen application." />
|
|
<item value="Fullscreen display with status and navigation bars presentable by tapping anywhere on the display. Available starting at SDK 16 or Android J. Earlier versions of Android will not be affected by this setting. For applications running on iOS, the status bar and home indicator will be hidden for a similar fullscreen experience. Tapping on the screen displays overlays, this gesture is not received by the application. See also: [SystemUiChangeCallback], used to listen and respond to the change in system overlays." />
|
|
<item value="landscape" />
|
|
<item value="portrait" />
|
|
<item value="If an IP version 6 (IPv6) address is used, both IP version 6 (IPv6) and version 4 (IPv4) connections will be accepted. To restrict this to version 6 (IPv6) only, use [v6Only] to set version 6 only. However, if the address is [InternetAddress.loopbackIPv6], only IP version 6 (IPv6) connections will be accepted." />
|
|
<item value="If [port] has the value 0 an ephemeral port will be chosen by the system. The actual port used can be retrieved using the [port] getter." />
|
|
<item value="The optional argument [backlog] can be used to specify the listen backlog for the underlying OS listen setup. If [backlog] has the value of 0 (the default) a reasonable value will be chosen by the system." />
|
|
<item value="The optional argument [shared] specifies whether additional `HttpServer` objects can bind to the same combination of `address`, `port` and `v6Only`. If `shared` is `true` and more `HttpServer`s from this isolate or other isolates are bound to the port, then the incoming connections will be distributed among all the bound `HttpServer`s. Connections can be distributed over multiple isolates this way." />
|
|
<item value="Looks up the addresses of a host. If [type] is [InternetAddressType.any], it will lookup both IP version 4 (IPv4) and IP version 6 (IPv6) addresses. If [type] is either [InternetAddressType.IPv4] or [InternetAddressType.IPv6] it will only lookup addresses of the specified type. The order of the list can, and most likely will, change over time." />
|
|
<item value="Handles errors emitted by this [Future]. This is the asynchronous equivalent of a "catch" block. Returns a new [Future] that will be completed with either the result of this future or the result of calling the `onError` callback. If this future completes with a value, the returned future completes with the same value. If this future completes with an error, then [test] is first called with the error value. If `test` returns false, the exception is not handled by this `catchError`, and the returned future completes with the same error and stack trace as this future. If `test` returns `true`, [onError] is called with the error and possibly stack trace, and the returned future is completed with the result of this call in exactly the same way as for [then]'s `onError`. If `test` is omitted, it defaults to a function that always returns true. The `test` function should not throw, but if it does, it is handled as if the `onError` function had thrown. Note that futures don't delay reporting of errors until listeners are added. If the first `catchError` (or `then`) call happens after this future has completed with an error then the error is reported as unhandled error. See the description on [Future]. Example: ```dart Future.delayed( const Duration(seconds: 1), () => throw 401, ).then((value) { throw 'Unreachable'; }).catchError((err) { print('Error: err'); Prints 401. }, test: (error) { return error is int && error >= 400; }); ``` The `Function` below stands for one of two types: - (dynamic) -> FutureOr<T> - (dynamic, StackTrace) -> FutureOr<T> Given that there is a `test` function that is usually used to do an `is` check, we should also expect functions that take a specific argument." />
|
|
<item value="If `test` returns `true`, [onError] is called with the error and possibly stack trace, and the returned future is completed with the result of this call in exactly the same way as for [then]'s `onError`." />
|
|
<item value="If `test` is omitted, it defaults to a function that always returns true. The `test` function should not throw, but if it does, it is handled as if the `onError` function had thrown." />
|
|
<item value="If [onError] is not given, and this future completes with an error, the error is forwarded directly to the returned future." />
|
|
<item value="If `eagerError` is true, the returned future completes with an error immediately on the first error from one of the futures. Otherwise all futures must complete before the returned future is completed (still with the first error; the remaining errors are silently dropped)." />
|
|
<item value="eager Error" />
|
|
<item value="A method returns a human readable string representing a file _size" />
|
|
<item value="[size] can be passed as number or as string the optional parameter [round] specifies the number of digits after commapoint (default is 2)" />
|
|
<item value="user Created" />
|
|
</histories>
|
|
<option name="languageScores">
|
|
<map>
|
|
<entry key="CHINESE" value="17" />
|
|
<entry key="ENGLISH" value="18" />
|
|
</map>
|
|
</option>
|
|
</component>
|
|
</application> |