<itemvalue="A class that efficiently implements both [Queue] and [List]."/>
<itemvalue="A [Queue] is a collection that can be manipulated at both ends. One can iterate over the elements of a queue through [forEach] or with an [Iterator]."/>
<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="Records a [Picture] containing a sequence of graphical operations. To begin recording, construct a [Canvas] to record the commands. To end recording, use the [PictureRecorder.endRecording] method. Use with the Flutter framework The Flutter framework's [RendererBinding] provides a hook for creating [PictureRecorder] objects ([RendererBinding.createPictureRecorder]) that allows tests to hook into the scene creation logic. When creating a [PictureRecorder] and [Canvas] that will be used with a [PictureLayer] as part of the [Scene] in the context of the Flutter framework, consider calling [RendererBinding.createPictureRecorder] instead of calling the [PictureRecorder.new] constructor directly. This does not apply when using a canvas to generate a bitmap for other purposes, e.g. for generating a PNG image using [Picture.toImage]."/>
debuggerx
4 weeks ago