<itemvalue="Creates a new repeating timer. The [callback] is invoked repeatedly with [duration] intervals until canceled with the [cancel] function. The exact timing depends on the underlying timer implementation. No more than `n` callbacks will be made in `duration n` time, but the time between two consecutive callbacks can be shorter and longer than `duration`. In particular, an implementation may schedule the next callback, e.g., a `duration` after either when the previous callback ended, when the previous callback started, or when the previous callback was scheduled for - even if the actual callback was delayed."/>
<itemvalue="Creates a new timer. The [callback] function is invoked after the given [duration]. Example: ```dart final timer = Timer(const Duration(seconds: 5), () => print('Timer finished')); Outputs after 5 seconds: "Timer finished". ```"/>
<itemvalue="A countdown timer that can be configured to fire once or repeatedly. The timer counts down from the specified duration to 0. When the timer reaches 0, the timer invokes the specified callback function. Use a periodic timer to repeatedly count down the same interval. A negative duration is treated the same as a duration of 0. If the duration is statically known to be 0, consider using [run]. Frequently the duration is either a constant or computed as in the following example (taking advantage of the multiplication operator of the [Duration] class): ```dart void main() { scheduleTimeout(5 1000); 5 seconds. } Timer scheduleTimeout([int milliseconds = 10000]) => Timer(Duration(milliseconds: milliseconds), handleTimeout); void handleTimeout() { callback function Do some work. } ``` Note: If Dart code using [Timer] is compiled to JavaScript, the finest granularity available in the browser is 4 milliseconds. See also: [Stopwatch] for measuring elapsed time."/>
<itemvalue="Seems .unityLibrarybuild.gradle has bean resolved"/>
<itemvalue="Skip resolve script because another process running"/>
<itemvalue="resolve"/>
@ -51,14 +54,11 @@
<itemvalue="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."/>
<itemvalue="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."/>
<itemvalue="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`."/>
<itemvalue="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."/>
<itemvalue="If [onError] is not given, and this future completes with an error, the error is forwarded directly to the returned future."/>
<itemvalue="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)."/>
