AndroidStudioSettings/yiiguxing.translation.xml

<application>
  <component name="Translation.Cache">
    <option name="lastTrimTime" value="1744699926944" />
  </component>
  <component name="Translation.OpenAISettings">
    <option name="OPEN_AI">
      <open-ai>
        <option name="API_PATH" value="/api/paas/v4/chat/completions" />
        <option name="CUSTOM_MODEL" value="glm-4-flash" />
        <option name="ENDPOINT" value="https://open.bigmodel.cn" />
        <option name="USE_CUSTOM_MODEL" value="true" />
      </open-ai>
    </option>
  </component>
  <component name="Translation.Settings">
    <option name="primaryLanguage" value="CHINESE_SIMPLIFIED" />
    <option name="translator" value="OPEN_AI" />
  </component>
  <component name="Translation.States">
    <histories>
      <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="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]." />
      <item value="A list whose items the user can interactively reorder by dragging. {@youtube 560 315 https:www.youtube.comwatch?v=3fB1mxOsqJE} This sample shows by dragging the user can reorder the items of the list. The [onReorder] parameter is required and will be called when a child widget is dragged to a new position." />
      <item value="move toolbox to side navigator." />
      <item value="emotion id" />
      <item value="If [allowImplicitScrolling] is true, the [PageView] will participate in accessibility scrolling more like a [ListView], where implicit scroll actions will move to the next page rather than into the contents of the [PageView]." />
      <item value="allow implicit scrolling" />
      <item value="Treat the [Viewport.cacheExtent] as a multiplier of the main axis extent." />
      <item value="Treat the [Viewport.cacheExtent] as logical pixels." />
      <item value="Controls whether the widget's pages will respond to [RenderObject.showOnScreen], which will allow for implicit accessibility scrolling. With this flag set to false, when accessibility focus reaches the end of the current page and the user attempts to move it to the next element, the focus will traverse to the next widget outside of the page view. With this flag set to true, when accessibility focus reaches the end of the current page and user attempts to move it to the next element, focus will traverse to the next page in the page view." />
      <item value="自定义指令" />
      <item value="{@template flutter.widgets.pageview.viewportFraction} The fraction of the viewport that each page should occupy. Defaults to 1.0, which means each page fills the viewport in the scrolling direction. {@endtemplate}" />
      <item value="set rc action internal" />
      <item value="我在" />
      <item value="有效数据" />
      <item value="amplitude" />
      <item value="64" />
      <item value="allow move the stick only in horizontal and vertical directions, not diagonal." />
      <item value="interaction text symbol black list" />
      <item value="优先级" />
      <item value="connection accepted" />
      <item value="unaccepted protocol version" />
      <item value="identifier rejected" />
      <item value="broker unavailable" />
      <item value="bad username or password" />
      <item value="not authorized" />
      <item value="none specified" />
      <item value="emoticon" />
      <item value="emotcion" />
      <item value="get emoticon list" />
      <item value="emoticon list" />
      <item value="standard" />
      <item value="calibrate" />
      <item value="Teleoperation" />
      <item value="start teleoperation" />
      <item value="Please operate the standby station to lower the robot until both feet of the robot are in full contact with the ground." />
      <item value="微笑" />
      <item value="smail" />
      <item value="比心" />
      <item value="握手" />
      <item value="bump" />
      <item value="taichi" />
      <item value="salute" />
      <item value="rl locomotion default disable" />
      <item value="Usually, this means that the Expanded widget has the wrong ancestor RenderObjectWidget. Typically, Expanded widgets are placed directly inside Flex widgets. The offending Expanded is currently placed inside a Opacity widget." />
      <item value="Draws a shadow for a [Path] representing the given material elevation. The `transparentOccluder` argument should be true if the occluding object is not opaque. The arguments must not be null." />
      <item value="A pointer that has triggered a long-press with a primary button has stopped contacting the screen." />
      <item value="A pointer that has triggered a long-press with a primary button has stopped contacting the screen. This is equivalent to (and is called immediately after) [onLongPressEnd]. The only difference between the two is that this callback does not contain details of the state of the pointer when it stopped contacting the screen." />
    </histories>
    <option name="languageScores">
      <map>
        <entry key="CHINESE_SIMPLIFIED" value="54" />
        <entry key="ENGLISH" value="54" />
      </map>
    </option>
  </component>
</application>