<itemvalue="Specifies which face detection model variant to use. Different models are optimized for different use cases: - [frontCamera]: Optimized for selfiefront-facing camera (128x128 input) - [backCamera]: Optimized for rear camera with higher resolution (256x256 input) - [shortRange]: Optimized for close-up faces (128x128 input) - [full]: Full-range detection (192x192 input) - [fullSparse]: Full-range with sparse anchors (192x192 input)"/>
<itemvalue="Shuffles the elements of this list randomly. ```dart final numbers = <int>[1, 2, 3, 4, 5]; numbers.shuffle(); print(numbers); [1, 3, 4, 5, 2] OR some other random result."/>
<itemvalue="The size of the rectangle is determined by its parent widget, and the texture is automatically scaled to fit."/>
<itemvalue="Texture widgets are repainted autonomously as dictated by the backend (e.g. on arrival of a video frame). Such repainting generally does not involve executing Dart code."/>
<itemvalue="A texture widget refers to its backend texture using an integer ID. Texture IDs are obtained from the texture registry and are scoped to the Flutter view. Texture IDs may be reused after deregistration, at the discretion of the registry. The use of texture IDs currently unknown to the registry will silently result in a blank rectangle."/>
<itemvalue="A rectangle upon which a backend texture is mapped. Backend textures are images that can be applied (mapped) to an area of the Flutter view. They are created, managed, and updated using a platform-specific texture registry. This is typically done by a plugin that integrates with host platform video player, camera, or OpenGL APIs, or similar image sources."/>
<itemvalue="See also: [push] which pushes the given location onto the page stack. [pushReplacement] which replaces the top-most page of the page stack but always uses a new page key."/>
<itemvalue="The page key will be reused. This will preserve the state and not run any page animation."/>
<itemvalue="Replaces the top-most page of the page stack with the given one but treats it as the same page."/>
<itemvalue="Replaces the top-most page of the page stack with the given URL location w optional query parameters, e.g. `familyf2personp1?color=blue`."/>
<itemvalue="Replaces the top-most page of the page stack with the given URL location w optional query parameters, e.g. `familyf2personp1?color=blue`. See also: [go] which navigates to the location. [push] which pushes the given location onto the page stack. [replace] which replaces the top-most page of the page stack but treats it as the same page. The page key will be reused. This will preserve the state and not run any page animation."/>
<itemvalue="Controls how one widget replaces another widget in the tree. If the [runtimeType] and [key] properties of the two widgets are [operator==], respectively, then the new widget replaces the old widget by updating the underlying element (i.e., by calling [Element.update] with the new widget). Otherwise, the old element is removed from the tree, the new widget is inflated into an element, and the new element is inserted into the tree. In addition, using a [GlobalKey] as the widget's [key] allows the element to be moved around the tree (changing parent) without losing state. When a new widget is found (its key and type do not match a previous widget in the same location), but there was a widget with that same global key elsewhere in the tree in the previous frame, then that widget's element is moved to the new location. Generally, a widget that is the only child of another widget does not need an explicit key. See also: The discussions at [Key] and [GlobalKey]."/>
<itemvalue="The absolute URI of the script being run in this isolate. If the script argument on the command line is relative, it is resolved to an absolute URI before fetching the script, and that absolute URI is returned. URI resolution only does string manipulation on the script path, and this may be different from the file system's path resolution behavior. For example, a symbolic link immediately followed by '..' will not be looked up. If a compiled Dart script is being executed the URI to the compiled script is returned, for example, `file:fullpathtoscript_name.exe`. If running on the Dart VM the URI to the running Dart script is returned, for example, `file:fullpathtoscript_name.dart`. If the executable environment does not support [script], the URI is empty."/>
<itemvalue="The path of the executable used to run the script in this isolate. Usually `dart` when running on the Dart VM or the compiled script name (`script_name.exe`). The literal path used to identify the executable. This path might be relative or just be a name from which the executable was found by searching the system path. Use [resolvedExecutable] to get an absolute path to the executable."/>
<itemvalue="The path of the executable used to run the script in this isolate after it has been resolved by the OS. This is the absolute path, with all symlinks resolved, to the executable used to run the script. See [executable] for the unresolved version."/>
<itemvalue="The initialization type can be dynamically set, which is suitable for some special scenarios; for example: for a desktop application, initializing the global only needs to initialize the Attach Dialog, and initializing a block area does not need to initialize the Attach Dialog 可动态设置初始化类型, 适用于一些特殊场景; 例如: 某桌面端应用, 初始化全局只需要初始化Attach Dialog, 初始化某块区域不需要初始化Attach Dialog"/>