<itemvalue="Whether this widget should prevent other [MouseRegion]s visually behind it from detecting the pointer. This changes the list of regions that a pointer hovers, thus affecting how their [onHover], [onEnter], [onExit], and [cursor] behave. If [opaque] is true, this widget will absorb the mouse pointer and prevent this widget's siblings (or any other widgets that are not ancestors or descendants of this widget) from detecting the mouse pointer even when the pointer is within their areas. If [opaque] is false, this object will not affect how [MouseRegion]s behind it behave, which will detect the mouse pointer as long as the pointer is within their areas. This defaults to true."/>
<itemvalue="Creates a widget that forwards mouse events to callbacks. By default, all callbacks are empty, [cursor] is [MouseCursor.defer], and [opaque] is true."/>
<itemvalue="Layout behavior _See [BoxConstraints] for an introduction to box layout models._ If it has a child, this widget defers to the child for sizing behavior. If it does not have a child, it grows to fit the parent instead. {@tool dartpad} This example makes a [Container] react to being entered by a mouse pointer, showing a count of the number of entries and exits. See code in examplesapilibwidgetsbasicmouse_region.0.dart {@end-tool} See also: [Listener], a similar widget that tracks pointer events when the pointer has buttons pressed."/>
<itemvalue="A widget that tracks the movement of mice. {@youtube 560 315 https:www.youtube.comwatch?v=1oF3pI5umck} [MouseRegion] is used when it is needed to compare the list of objects that a mouse pointer is hovering over between this frame and the last frame. This means entering events, exiting events, and mouse cursors. To listen to general pointer events, use [Listener], or more preferably, [GestureDetector]."/>
<itemvalue="elevator wait"/>
<itemvalue="elevator wait"/>
<itemvalue="电梯排队中"/>
<itemvalue="电梯排队中"/>
<itemvalue="All list items must have a key. This example demonstrates using the [ReorderableListView.proxyDecorator] callback to customize the appearance of a list item while it's being dragged."/>
<itemvalue="All list items must have a key. This example demonstrates using the [ReorderableListView.proxyDecorator] callback to customize the appearance of a list item while it's being dragged."/>
@ -58,16 +62,12 @@
<itemvalue="chassis status notifier"/>
<itemvalue="chassis status notifier"/>
<itemvalue="collect data"/>
<itemvalue="collect data"/>
<itemvalue="The following defines the version and build number for your application. A version number is three numbers separated by dots, like 1.2.43 followed by an optional build number separated by a +. Both the version and the builder number may be overridden in flutter build by specifying --build-name and --build-number, respectively. In Android, build-name is used as versionName while build-number used as versionCode. Read more about Android versioning at https:developer.android.comstudiopublishversioning In iOS, build-name is used as CFBundleShortVersionString while build-number is used as CFBundleVersion. Read more about iOS versioning at https:developer.apple.comlibraryarchivedocumentationGeneralReferenceInfoPlistKeyReferenceArticlesCoreFoundationKeys.html In Windows, build-name is used as the major, minor, and patch parts of the product and file versions while build-number is used as the build suffix."/>
<itemvalue="The following defines the version and build number for your application. A version number is three numbers separated by dots, like 1.2.43 followed by an optional build number separated by a +. Both the version and the builder number may be overridden in flutter build by specifying --build-name and --build-number, respectively. In Android, build-name is used as versionName while build-number used as versionCode. Read more about Android versioning at https:developer.android.comstudiopublishversioning In iOS, build-name is used as CFBundleShortVersionString while build-number is used as CFBundleVersion. Read more about iOS versioning at https:developer.apple.comlibraryarchivedocumentationGeneralReferenceInfoPlistKeyReferenceArticlesCoreFoundationKeys.html In Windows, build-name is used as the major, minor, and patch parts of the product and file versions while build-number is used as the build suffix."/>