<itemvalue="The divider's height extent. The divider itself is always drawn as a horizontal line that is centered within the height specified by this value. If this is null, then the [DividerThemeData.space] is used. If that is also null, then this defaults to 16.0."/>
<itemvalue="The thickness of the line drawn within the divider. A divider with a [thickness] of 0.0 is always drawn as a line with a height of exactly one device pixel. If this is null, then the [DividerThemeData.thickness] is used. If that is also null, then this defaults to 0.0."/>
<itemvalue="Used to annotate a field that is allowed to be overridden in Strong Mode. Deprecated: Most of strong mode is now the default in 2.0, but the notion of virtual fields was dropped, so this annotation no longer has any meaning. Uses of the annotation should be removed."/>
<itemvalue="Used to annotate a field that is allowed to be overridden in Strong Mode. Deprecated: Most of strong mode is now the default in 2.0, but the notion of virtual fields was dropped, so this annotation no longer has any meaning. Uses of the annotation should be removed."/>
<itemvalue="Used to annotate an instance member (method, getter, setter, operator, or field) `m` in a class `C` or mixin `M`. Indicates that `m` should not be overridden in any classes that extend or mixin `C` or `M`. Tools, such as the analyzer, can provide feedback if the annotation is associated with anything other than an instance member, the annotation is associated with an abstract member (because subclasses are required to override the member), the annotation is associated with an extension method, the annotation is associated with a member `m` in class `C`, and there is a class `D` or mixin `M`, that extends or mixes in `C`, that declares an overriding member `m`."/>
<itemvalue="Used to annotate an instance member (method, getter, setter, operator, or field) `m` in a class `C` or mixin `M`. Indicates that `m` should not be overridden in any classes that extend or mixin `C` or `M`. Tools, such as the analyzer, can provide feedback if the annotation is associated with anything other than an instance member, the annotation is associated with an abstract member (because subclasses are required to override the member), the annotation is associated with an extension method, the annotation is associated with a member `m` in class `C`, and there is a class `D` or mixin `M`, that extends or mixes in `C`, that declares an overriding member `m`."/>
<itemvalue="w"/>
<itemvalue="w"/>
@ -52,13 +54,11 @@
<itemvalue="Event model Flutter uses a universal event model ([KeyEvent]) and key options ([LogicalKeyboardKey] and [PhysicalKeyboardKey]) regardless of the native platform, while preserving platform-specific features as much as possible. [HardwareKeyboard] guarantees that the key model is "regularized": The key event stream consists of "key tap sequences", where a key tap sequence is defined as one [KeyDownEvent], zero or more [KeyRepeatEvent]s, and one [KeyUpEvent"/>
<itemvalue="Event model Flutter uses a universal event model ([KeyEvent]) and key options ([LogicalKeyboardKey] and [PhysicalKeyboardKey]) regardless of the native platform, while preserving platform-specific features as much as possible. [HardwareKeyboard] guarantees that the key model is "regularized": The key event stream consists of "key tap sequences", where a key tap sequence is defined as one [KeyDownEvent], zero or more [KeyRepeatEvent]s, and one [KeyUpEvent"/>
<itemvalue="Manages key events from hardware keyboards. [HardwareKeyboard] manages all key events of the Flutter application from hardware keyboards (in contrast to on-screen keyboards). It receives key data from the native platform, dispatches key events to registered handlers, and records the keyboard state. To stay notified whenever keys are pressed, held, or released, add a handler with [addHandler]. To only be notified when a specific part of the app is focused, use a [Focus] widget's `onFocusChanged` attribute instead of [addHandler]. Handlers should be removed with [removeHandler] when notification is no longer necessary, or when the handler is being disposed. To query whether a key is being held, or a lock mode is enabled, use [physicalKeysPressed], [logicalKeysPressed], or [lockModesEnabled]. These states will have been updated with the event when used during a key event handler. The singleton [HardwareKeyboard] instance is held by the [ServicesBinding] as [ServicesBinding.keyboard], and can be conveniently accessed using the [HardwareKeyboard.instance] static accessor."/>
<itemvalue="Manages key events from hardware keyboards. [HardwareKeyboard] manages all key events of the Flutter application from hardware keyboards (in contrast to on-screen keyboards). It receives key data from the native platform, dispatches key events to registered handlers, and records the keyboard state. To stay notified whenever keys are pressed, held, or released, add a handler with [addHandler]. To only be notified when a specific part of the app is focused, use a [Focus] widget's `onFocusChanged` attribute instead of [addHandler]. Handlers should be removed with [removeHandler] when notification is no longer necessary, or when the handler is being disposed. To query whether a key is being held, or a lock mode is enabled, use [physicalKeysPressed], [logicalKeysPressed], or [lockModesEnabled]. These states will have been updated with the event when used during a key event handler. The singleton [HardwareKeyboard] instance is held by the [ServicesBinding] as [ServicesBinding.keyboard], and can be conveniently accessed using the [HardwareKeyboard.instance] static accessor."/>
<itemvalue="A widget that calls a callback whenever the user presses or releases a key on a keyboard. A [RawKeyboardListener] is useful for listening to raw key events and hardware buttons that are represented as keys. Typically used by games and other apps that use keyboards for purposes other than text entry. For text entry, consider using a [EditableText], which integrates with on-screen keyboards and input method editors (IMEs). The [RawKeyboardListener] is different from [KeyboardListener] in that [RawKeyboardListener] uses the legacy [RawKeyboard] API. Use [KeyboardListener] if possible. See also: [EditableText], which should be used instead of this widget for text entry. [KeyboardListener], a similar widget based on the newer [HardwareKeyboard] API."/>
<itemvalue="A widget that calls a callback whenever the user presses or releases a key on a keyboard. A [RawKeyboardListener] is useful for listening to raw key events and hardware buttons that are represented as keys. Typically used by games and other apps that use keyboards for purposes other than text entry. For text entry, consider using a [EditableText], which integrates with on-screen keyboards and input method editors (IMEs). The [RawKeyboardListener] is different from [KeyboardListener] in that [RawKeyboardListener] uses the legacy [RawKeyboard] API. Use [KeyboardListener] if possible. See also: [EditableText], which should be used instead of this widget for text entry. [KeyboardListener], a similar widget based on the newer [HardwareKeyboard] API."/>
<itemvalue="Specify that the automatic animation should repeat in a loop (default to true). The property has no effect if [animate] is false or [controller] is not null."/>
<itemvalue="Indicate to automatically add a `RepaintBoundary` widget around the animation. This allows to optimize the app performance by isolating the animation in its own `Layer`. This property is `true` by default."/>
