<itemvalue="Whether this range is empty (but still potentially placed inside the text)."/>
<itemvalue="Push a URI location onto the page stack w optional query parameters, e.g. `familyf2personp1?color=blue`. See also: [pushReplacement] which replaces the top-most page of the page stack and always use a new page key. [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="A common pattern when using bottom navigation bars is to support navigating to the initial location when tapping the item that is already active. This example demonstrates how to support this behavior, using the initialLocation parameter of goBranch."/>
<itemvalue="When navigating to a new branch, it's recommended to use the goBranch method, as doing so makes sure the last navigation state of the Navigator for the branch is restored."/>
@ -19,7 +20,6 @@
<itemvalue="Clip with anti-aliasing. This mode has anti-aliased clipping edges to achieve a smoother look. It' s much faster than [antiAliasWithSaveLayer], but slower than [hardEdge]. This will be the common case when dealing with circles and arcs. Different from [hardEdge] and [antiAliasWithSaveLayer], this clipping may have bleeding edge artifacts. (See https:fiddle.skia.orgc21cb4c2b2515996b537f36e7819288ae for an example.) See also: [hardEdge], which is a little faster, but with lower fidelity. [antiAliasWithSaveLayer], which is much slower, but can avoid the bleeding edges if there's no other way. [Paint.isAntiAlias], which is the anti-aliasing switch for general draw operations."/>
<itemvalue="Clip, but do not apply anti-aliasing. This mode enables clipping, but curves and non-axis-aligned straight lines will be jagged as no effort is made to anti-alias. Faster than other clipping modes, but slower than [none]. This is a reasonable choice when clipping is needed, if the container is an axis- aligned rectangle or an axis-aligned rounded rectangle with very small corner radii. See also: [antiAlias], which is more reasonable when clipping is needed and the shape is not an axis-aligned rectangle."/>
<itemvalue="No clip at all. This is the default option for most widgets: if the content does not overflow the widget boundary, don't pay any performance cost for clipping. If the content does overflow, please explicitly specify the following [Clip] options: [hardEdge], which is the fastest clipping, but with lower fidelity. [antiAlias], which is a little slower than [hardEdge], but with smoothed edges. [antiAliasWithSaveLayer], which is much slower than [antiAlias], and should rarely be used."/>
<itemvalue="Whether this range is empty (but still potentially placed inside the text)."/>
<itemvalue="Whether the start of this range precedes the end."/>
<itemvalue="Whether this range represents a valid position in the text."/>
<itemvalue="The range of text that is still being composed. Composing regions are created by input methods (IMEs) to indicate the text within a certain range is provisional. For instance, the Android Gboard app's English keyboard puts the current word under the caret into a composing region to indicate the word is subject to autocorrect or prediction changes. Composing regions can also be used for performing multistage input, which is typically used by IMEs designed for phonetic keyboard to enter ideographic symbols. As an example, many CJK keyboards require the user to enter a Latin alphabet sequence and then convert it to CJK characters. On iOS, the default software keyboards do not have a dedicated view to show the unfinished Latin sequence, so it's displayed directly in the text field, inside of a composing region. The composing region should typically only be changed by the IME, or the user via interacting with the IME. If the range represented by this property is [TextRange.empty], then the text is not currently being composed."/>
dx
1 year ago