<itemvalue="A widget that defines a region that can detect taps inside or outside of itself and any group of regions it belongs to, without participating in the [gesture disambiguation](https:flutter.devgesturesgesture-disambiguation) system (other than to consume tap down events if [consumeOutsideTaps] is true). This widget indicates to the nearest ancestor [TapRegionSurface] that the region occupied by its child will participate in the tap detection for that surface. If this region belongs to a group (by virtue of its [groupId]), all the regions in the group will act as one. If there is no [TapRegionSurface] ancestor, [TapRegion] will do nothing."/>
<itemvalue="A [TapRegion] that adds its children to the tap region group for widgets based on the [EditableText] text editing widget, such as [TextField] and [CupertinoTextField]. Widgets that are wrapped with a [TextFieldTapRegion] are considered to be part of a text field for purposes of unfocus behavior. So, when the user taps on them, the currently focused text field won't be unfocused by default. This allows controls like spinners, copy buttons, and formatting buttons to be associated with a text field without causing the text field to lose focus when they are interacted with. {@tool dartpad} This example shows how to use a [TextFieldTapRegion] to wrap a set of "spinner" buttons that increment and decrement a value in the text field without causing the text field to lose keyboard focus. This example includes a generic `SpinnerField<T>` class that you can copypaste into your own project and customize. See code in examplesapilibwidgetstap_regiontext_field_tap_region.0.dart {@end-tool} See also: [TapRegion], the widget that this widget uses to add widgets to the group of text fields."/>
<itemvalue="A [TapRegion] that adds its children to the tap region group for widgets based on the [EditableText] text editing widget, such as [TextField] and [CupertinoTextField]. Widgets that are wrapped with a [TextFieldTapRegion] are considered to be part of a text field for purposes of unfocus behavior. So, when the user taps on them, the currently focused text field won't be unfocused by default. This allows controls like spinners, copy buttons, and formatting buttons to be associated with a text field without causing the text field to lose focus when they are interacted with. {@tool dartpad} This example shows how to use a [TextFieldTapRegion] to wrap a set of "spinner" buttons that increment and decrement a value in the text field without causing the text field to lose keyboard focus. This example includes a generic `SpinnerField<T>` class that you can copypaste into your own project and customize. See code in examplesapilibwidgetstap_regiontext_field_tap_region.0.dart {@end-tool} See also: [TapRegion], the widget that this widget uses to add widgets to the group of text fields."/>
<itemvalue="An interface for implementing text input controls that receive text editing state changes and visual input control requests. Editing state changes and input control requests are sent by the framework when the editing state of the attached text input client changes, or it requests the input control to be shown or hidden, for example. The input control can be installed with [TextInput.setInputControl], and the default platform text input control can be restored with [TextInput.restorePlatformInputControl]. The [TextInputControl] class must be extended. [TextInputControl] implementations should call [TextInput.updateEditingValue] to send user input to the attached input client."/>
<itemvalue="An interface for implementing text input controls that receive text editing state changes and visual input control requests. Editing state changes and input control requests are sent by the framework when the editing state of the attached text input client changes, or it requests the input control to be shown or hidden, for example. The input control can be installed with [TextInput.setInputControl], and the default platform text input control can be restored with [TextInput.restorePlatformInputControl]. The [TextInputControl] class must be extended. [TextInputControl] implementations should call [TextInput.updateEditingValue] to send user input to the attached input client."/>
<itemvalue="A widget that absorbs pointers during hit testing. When [absorbing] is true, this widget prevents its subtree from receiving pointer events by terminating hit testing at itself. It still consumes space during layout and paints its child as usual. It just prevents its children from being the target of located events, because it returns true from [RenderBox.hitTest]."/>
<itemvalue="A widget that absorbs pointers during hit testing. When [absorbing] is true, this widget prevents its subtree from receiving pointer events by terminating hit testing at itself. It still consumes space during layout and paints its child as usual. It just prevents its children from being the target of located events, because it returns true from [RenderBox.hitTest]."/>
@ -60,12 +61,11 @@
<itemvalue="{@template dio.CancelToken} Controls cancellation of [Dio]'s requests. The same token can be shared between different requests. When [cancel] is invoked, requests bound to this token will be cancelled. {@endtemplate}"/>
<itemvalue="{@template dio.CancelToken} Controls cancellation of [Dio]'s requests. The same token can be shared between different requests. When [cancel] is invoked, requests bound to this token will be cancelled. {@endtemplate}"/>
<itemvalue="An optional maximum number of lines for the text to span, wrapping if necessary. If the text exceeds the given number of lines, it will be truncated according to [overflow]. If this is 1, text will not wrap. Otherwise, text will be wrapped at the edge of the box. If this is null, but there is an ambient [DefaultTextStyle] that specifies an explicit number for its [DefaultTextStyle.maxLines], then the [DefaultTextStyle] value will take precedence. You can use a [RichText] widget directly to entirely override the [DefaultTextStyle]."/>
<itemvalue="An optional maximum number of lines for the text to span, wrapping if necessary. If the text exceeds the given number of lines, it will be truncated according to [overflow]. If this is 1, text will not wrap. Otherwise, text will be wrapped at the edge of the box. If this is null, but there is an ambient [DefaultTextStyle] that specifies an explicit number for its [DefaultTextStyle.maxLines], then the [DefaultTextStyle] value will take precedence. You can use a [RichText] widget directly to entirely override the [DefaultTextStyle]."/>
<itemvalue="Whether to show or hide a child. By default, the [visible] property controls whether the [child] is included in the subtree or not; when it is not [visible], the [replacement] child (typically a zero-sized box) is included instead. A variety of flags can be used to tweak exactly how the child is hidden. (Changing the flags dynamically is discouraged, as it can cause the [child] subtree to be rebuilt, with any state in the subtree being discarded. Typically, only the [visible] flag is changed dynamically.)"/>
<itemvalue="Whether to show or hide a child. By default, the [visible] property controls whether the [child] is included in the subtree or not; when it is not [visible], the [replacement] child (typically a zero-sized box) is included instead. A variety of flags can be used to tweak exactly how the child is hidden. (Changing the flags dynamically is discouraged, as it can cause the [child] subtree to be rebuilt, with any state in the subtree being discarded. Typically, only the [visible] flag is changed dynamically.)"/>
<itemvalue="An optional maximum number of lines for the text to span, wrapping if necessary. If the text exceeds the given number of lines, it will be truncated according to [overflow]. If this is 1, text will not wrap. Otherwise, text will be wrapped at the edge of the box. If this is non-null, it will override even explicit null values of [Text.maxLines]."/>
debuggerx
11 months ago