<itemvalue="If `mode` is [ProcessStartMode.detached] a detached process will be created. A detached process has no connection to its parent, and can keep running on its own when the parent dies. The only information available from a detached process is its `pid`. There is no connection to its `stdin`, `stdout` or `stderr`, nor will the process' exit code become available when it terminates."/>
<itemvalue="If [mode] is [ProcessStartMode.normal] (the default) a child process will be started with `stdin`, `stdout` and `stderr` connected to its parent. The parent process will not exit so long as the child is running, unless [exit] is called by the parent. If [exit] is called by the parent then the parent will be terminated but the child will continue running."/>
<itemvalue="Using an absolute path for [executable] is recommended since resolving the [executable] path is platform-specific. On Windows, both any `PATH` set in the [environment] map parameter and the path set in [workingDirectory] parameter are ignored for the purposes of resolving the [executable] path."/>
<itemvalue="Returns a `Future<Process>` that completes with a [Process] instance when the process has been successfully started. That [Process] object can be used to interact with the process. If the process cannot be started the returned [Future] completes with an exception."/>
<itemvalue="Starts a process running the [executable] with the specified [arguments]."/>
<itemvalue="Resolves this image provider using the given `configuration`, returning an [ImageStream]. This is the public entry-point of the [ImageProvider] class hierarchy. Subclasses should implement [obtainKey] and [loadImage], which are used by this method. If they need to change the implementation of [ImageStream] used, they should override [createStream]. If they need to manage the actual resolution of the image, they should override [resolveStreamForKey]. See the Lifecycle documentation on [ImageProvider] for more information."/>
<itemvalue="was synchronously loaded"/>
<itemvalue="If a [loadingBuilder] has _also_ been specified for an image, the two builders will be chained together: the _result_ of this builder will be passed as the `child` argument to the [loadingBuilder]. For example, consider the following builders used in conjunction:"/>
@ -67,11 +72,6 @@
<itemvalue="Converts [input] to an YAML document as [String]. This implements `dart:convert` [Converter]. - Calls [write]."/>
<itemvalue="[toEncodable] is called to encode non-builtin classes."/>
<itemvalue="If [allowUnquotedStrings] is set, strings are written without quotes if possible."/>
<itemvalue="allow unquoted strings"/>
<itemvalue="Initialize the gradient's colors and stops. The [colors] argument must have at least two colors (the length is not verified until the [createShader] method is called). If specified, the [stops] argument must have the same number of entries as [colors] (this is also not verified until the [createShader] method is called). The [transform] argument can be applied to transform _only_ the gradient, without rotating the canvas itself or other geometry on the canvas. For example, a `GradientRotation(math.pi4)` will result in a [SweepGradient] that starts from a position of 6 o'clock instead of 3 o'clock, assuming no other rotation or perspective transformations have been applied to the [Canvas]. If null, no transformation is applied."/>