<itemvalue="Sends the current composing rect to the iOS text input plugin via the text input channel. We need to keep sending the information even if no text is currently marked, as the information usually lags behind. The text input plugin needs to estimate the composing rect based on the latest caret rect, when the composing rect info didn't arrive in time."/>
<itemvalue="Returns a list of rects that bound the given selection. The [boxHeightStyle] and [boxWidthStyle] arguments may be used to select the shape of the [TextBox]s. These properties default to [ui.BoxHeightStyle.tight] and [ui.BoxWidthStyle.tight] respectively and must not be null. A given selection might have more than one rect if this text painter contains bidirectional text because logically contiguous text might not be visually contiguous. Leading or trailing newline characters will be represented by zero-width `Textbox`es. The method only returns `TextBox`es of glyphs that are entirely enclosed by the given `selection`: a multi-code-unit glyph will be excluded if only part of its code units are in `selection`."/>
<itemvalue="Send the caret location instead if there's no marked text yet."/>
<itemvalue="Send the caret location instead if there's no marked text yet."/>
<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 phoetic 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."/>
<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 phoetic 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."/>
<itemvalue="Sends the current composing rect to the iOS text input plugin via the text input channel. We need to keep sending the information even if no text is currently marked, as the information usually lags behind. The text input plugin needs to estimate the composing rect based on the latest caret rect, when the composing rect info didn't arrive in time."/>
<itemvalue="tab切换时背景颜色平滑变化"/>
<itemvalue="tab切换时背景颜色平滑变化"/>
<itemvalue="tab切换时背景颜色平滑渐变"/>
<itemvalue="tab切换时背景颜色平滑渐变"/>
<itemvalue="Whether any listeners are currently registered. Clients should not depend on this value for their behavior, because having one listener's logic change when another listener happens to start or stop listening will lead to extremely hard-to-track bugs. Subclasses might use this information to determine whether to do any work when there are no listeners, however; for example, resuming a [Stream] when a listener is added and pausing it when a listener is removed. Typically this is used by overriding [addListener], checking if [hasListeners] is false before calling `super.addListener()`, and if so, starting whatever work is needed to determine when to call [notifyListeners]; and similarly, by overriding [removeListener], checking if [hasListeners] is false after calling `super.removeListener()`, and if so, stopping that same work."/>
<itemvalue="Whether any listeners are currently registered. Clients should not depend on this value for their behavior, because having one listener's logic change when another listener happens to start or stop listening will lead to extremely hard-to-track bugs. Subclasses might use this information to determine whether to do any work when there are no listeners, however; for example, resuming a [Stream] when a listener is added and pausing it when a listener is removed. Typically this is used by overriding [addListener], checking if [hasListeners] is false before calling `super.addListener()`, and if so, starting whatever work is needed to determine when to call [notifyListeners]; and similarly, by overriding [removeListener], checking if [hasListeners] is false after calling `super.removeListener()`, and if so, stopping that same work."/>
@ -55,12 +56,11 @@
<itemvalue="The ParentDataWidget Expanded(flex: 1) wants to apply ParentData of type FlexParentData to a Iflutter (30455): RenderObject, which has been set up to accept ParentData of incompatible type StackParentData. Iflutter (30455): Usually, this means that the Expanded widget has the wrong ancestor RenderObjectWidget. Typically, Iflutter (30455): Expanded widgets are placed directly inside Flex widgets. Iflutter (30455): The offending Expanded is currently placed inside a Stack widget. Iflutter (30455): The ownership chain for the RenderObject that received the incompatible parent data was: Iflutter (30455): SizedBox.expand ← Expanded ← GroupChatMessagesListView<GroupChatMessagesRecord> ← Stack ← Iflutter (30455): GetBuilder<GroupChatMessagesListController> ← GroupChatMessagesList ← Expanded ← Column ← MediaQuery Iflutter (30455): ← Padding ← ⋯"/>
<itemvalue="The ParentDataWidget Expanded(flex: 1) wants to apply ParentData of type FlexParentData to a Iflutter (30455): RenderObject, which has been set up to accept ParentData of incompatible type StackParentData. Iflutter (30455): Usually, this means that the Expanded widget has the wrong ancestor RenderObjectWidget. Typically, Iflutter (30455): Expanded widgets are placed directly inside Flex widgets. Iflutter (30455): The offending Expanded is currently placed inside a Stack widget. Iflutter (30455): The ownership chain for the RenderObject that received the incompatible parent data was: Iflutter (30455): SizedBox.expand ← Expanded ← GroupChatMessagesListView<GroupChatMessagesRecord> ← Stack ← Iflutter (30455): GetBuilder<GroupChatMessagesListController> ← GroupChatMessagesList ← Expanded ← Column ← MediaQuery Iflutter (30455): ← Padding ← ⋯"/>
debuggerx
3 years ago