AI-Meerkat | 2024.3.1 Patch 2 <debuggerx@debuggerx-PC Update yiiguxing.translation.xml

master
debuggerx 4 weeks ago
parent edf4ebab4a
commit 471eaaddc7

@ -18,6 +18,7 @@
</component> </component>
<component name="Translation.States"> <component name="Translation.States">
<histories> <histories>
<item value="Reorderable (drag and drop) version of [Wrap], A widget that displays its children in multiple horizontal or vertical runs. In addition to [Wrap]'s parameters, this widget also adds two parameters, [minMainAxisCount] and [maxMainAxisCount], that limits how many children each run has at least and at most. For example, if the size of parent widget allows a run to have more than [maxMainAxisCount] children, the run is forced to end and will have [maxMainAxisCount] children only. All [children] must have a key. See also: [Wrap], which displays its children in multiple horizontal or vertical runs." />
<item value="The reserved word `null` denotes an object that is the sole instance of this class. The `Null` class is the only class which does not implement `Object`. It is a compile-time error for a class to attempt to extend or implement [Null]. The language contains a number of specialized operators for working with `null` value. Examples: ```dart e1! Throws if e1 is null. e2 ?? e3 Same as e2, unless e2 is null, then use value of e3 x ??= e4 Same as x unless x is null, then same as `x = e4`. e5?.foo() call `foo` on e5, unless e5 is null. [...? e6] spreads e6 into the list literal, unless e6 is null. ```" /> <item value="The reserved word `null` denotes an object that is the sole instance of this class. The `Null` class is the only class which does not implement `Object`. It is a compile-time error for a class to attempt to extend or implement [Null]. The language contains a number of specialized operators for working with `null` value. Examples: ```dart e1! Throws if e1 is null. e2 ?? e3 Same as e2, unless e2 is null, then use value of e3 x ??= e4 Same as x unless x is null, then same as `x = e4`. e5?.foo() call `foo` on e5, unless e5 is null. [...? e6] spreads e6 into the list literal, unless e6 is null. ```" />
<item value="Typically set to true when the [InputDecorator] contains a multiline [TextField] ([TextField.maxLines] is null or &gt; 1) to override the default behavior of aligning the label with the center of the [TextField]. Defaults to false." /> <item value="Typically set to true when the [InputDecorator] contains a multiline [TextField] ([TextField.maxLines] is null or &gt; 1) to override the default behavior of aligning the label with the center of the [TextField]. Defaults to false." />
<item value="The direction to use for the [hintText]. If null, defaults to a value derived from [Directionality] for the input field and the current context." /> <item value="The direction to use for the [hintText]. If null, defaults to a value derived from [Directionality] for the input field and the current context." />
@ -67,7 +68,6 @@
<item value="If true: on desktop platforms, a drag handle is stacked over the center of each item's trailing edge; on mobile platforms, a long press anywhere on the item starts a drag. The default desktop drag handle is just an [Icons.drag_handle] wrapped by a [ReorderableDragStartListener]. On mobile platforms, the entire item is wrapped with a [ReorderableDelayedDragStartListener]. To change the appearance or the layout of the drag handles, make this parameter false and wrap each list item, or a widget within each list item, with [ReorderableDragStartListener] or [ReorderableDelayedDragStartListener], or a custom subclass of [ReorderableDragStartListener]. The following sample specifies `buildDefaultDragHandles: false`, and uses a [Card] at the leading edge of each item for the item's drag handle. {@tool dartpad} See code in examplesapilibmaterialreorderable_listreorderable_list_view.build_default_drag_handles.0.dart {@end-tool}" /> <item value="If true: on desktop platforms, a drag handle is stacked over the center of each item's trailing edge; on mobile platforms, a long press anywhere on the item starts a drag. The default desktop drag handle is just an [Icons.drag_handle] wrapped by a [ReorderableDragStartListener]. On mobile platforms, the entire item is wrapped with a [ReorderableDelayedDragStartListener]. To change the appearance or the layout of the drag handles, make this parameter false and wrap each list item, or a widget within each list item, with [ReorderableDragStartListener] or [ReorderableDelayedDragStartListener], or a custom subclass of [ReorderableDragStartListener]. The following sample specifies `buildDefaultDragHandles: false`, and uses a [Card] at the leading edge of each item for the item's drag handle. {@tool dartpad} See code in examplesapilibmaterialreorderable_listreorderable_list_view.build_default_drag_handles.0.dart {@end-tool}" />
<item value="{@macro flutter.widgets.list_view.prototypeItem} final Widget? prototypeItem;" /> <item value="{@macro flutter.widgets.list_view.prototypeItem} final Widget? prototypeItem;" />
<item value="This example demonstrates using the [ReorderableListView.proxyDecorator] callback to customize the appearance of a list item while it's being dragged." /> <item value="This example demonstrates using the [ReorderableListView.proxyDecorator] callback to customize the appearance of a list item while it's being dragged." />
<item value="By default, on [TargetPlatformVariant.desktop] platforms each item will have a drag handle added on top of it that will allow the user to grab it to move the item. On [TargetPlatformVariant.mobile], no drag handle will be added, but when the user long presses anywhere on the item it will start moving the item. Displaying drag handles can be controlled with [ReorderableListView.buildDefaultDragHandles]." />
</histories> </histories>
<option name="languageScores"> <option name="languageScores">
<map> <map>

Loading…
Cancel
Save