AI-Koala | 2024.1.1 Patch 1 <debuggerx@debuggerx-PC Update yiiguxing.translation.xml

master
debuggerx 9 months ago
parent c9d9eae1ce
commit 711b722f18

@ -12,6 +12,17 @@
<option name="translationDialogLocationY" value="536" />
<option name="translationDialogWidth" value="1253" />
<histories>
<item value="Return the distance from the origin of this to the intersection with [other] if this intersects with [other], or null if the don't intersect." />
<item value="intersects with triangle" />
<item value="On success, [rayNear] and [rayFar] are the points where the screen space [pickX], [pickY] intersect with the near and far planes respectively. The viewport is specified by ([viewportX], [viewportWidth]) and ([viewportY], [viewportHeight]). [cameraMatrix] includes both the projection and view transforms. Returns false on error, for example, the mouse is not in the viewport." />
<item value="pick ray" />
<item value="culling" />
<item value="is clipped face" />
<item value="add texture coordinates to renderMesh" />
<item value="perspective" />
<item value="apply perspective to screen transform" />
<item value="calculate the total number of vertices and faces" />
<item value="calculate vertices" />
<item value="The `blendMode` parameter is used to control how the colors in the `vertices` are combined with the colors in the `paint`. If there are no colors specified in `vertices` then the `blendMode` has no effect. If there are colors in the `vertices`, then the color taken from the [Paint.shader] or [Paint.color] in the `paint` is blended with the colors specified in the `vertices` using the `blendMode` parameter. For the purposes of this blending, the colors from the `paint` parameter are considered the source, and the colors from the `vertices` are considered the destination. [BlendMode.dst] ignores the `paint` and uses only the colors of the `vertices`; [BlendMode.src] ignores the colors of the `vertices` and uses only the colors in the `paint`." />
<item value="If the `indices` parameter is specified, all values in the list must be valid index values for pairs in `positions`. For example, if there are 12 numbers in `positions` (representing 6 coordinates), the `indicies` must be numbers in the range 0..5 inclusive. The `mode` and `positions` parameters must not be null." />
<item value="The `positions` parameter provides the points in the canvas space that will be use to draw the triangles. Each point is represented as two numbers in the list, the first giving the x coordinate and the second giving the y coordinate. (As a result, the list must have an even number of entries.)" />
@ -51,22 +62,11 @@
<item value="add cons" />
<item value="add typed literal" />
<item value="add type literal" />
<item value="add type parameter" />
<item value="add type parameter list" />
<item value="add uri based directive" />
<item value="add variable declaration" />
<item value="&quot;node&quot; exposes metadata about the variable declaration. We could check &quot;node&quot; to show the lint only in some conditions. This line tells custom_lint to render a warning at the location of &quot;node&quot;. And the warning shown will use our `code` variable defined above as description." />
<item value="Whether to exclude these gestures from the semantics tree. For example, the long-press gesture for showing a tooltip is excluded because the tooltip itself is included in the semantics tree directly and so having a gesture to show it would result in duplication of information." />
<item value="The velocity of the last pointer to be lifted off of the screen." />
<item value="The velocity the pointer was moving when it stopped contacting the screen. Defaults to zero if not specified in the constructor." />
<item value="The pointer's velocity when it stopped contacting the screen. Defaults to zero if not specified in the constructor." />
<item value="A widget that imposes no constraints on its child, allowing it to render at its &quot;natural&quot; size. This allows a child to render at the size it would render if it were alone on an infinite canvas with no constraints. This container will then attempt to adopt the same size, within the limits of its own constraints. If it ends up with a different size, it will align the child based on [alignment]. If the box cannot expand enough to accommodate the entire child, the child will be clipped. In debug mode, if the child overflows the container, a warning will be printed on the console, and black and yellow striped areas will appear where the overflow occurs." />
<item value="[ConstrainedBox], for a box which imposes constraints on its child. [Align], which loosens the constraints given to the child rather than removing them entirely. [Container], a convenience widget that combines common painting, positioning, and sizing widgets. [OverflowBox], a widget that imposes different constraints on its child than it gets from its parent, possibly allowing the child to overflow the parent. [ConstraintsTransformBox], a widget that sizes its child using a transformed [BoxConstraints], and shows a warning if the child overflows in debug mode." />
</histories>
<option name="languageScores">
<map>
<entry key="CHINESE" value="571" />
<entry key="ENGLISH" value="572" />
<entry key="CHINESE" value="583" />
<entry key="ENGLISH" value="584" />
<entry key="HAWAIIAN" value="1" />
<entry key="POLISH" value="1" />
<entry key="ROMANIAN" value="1" />

Loading…
Cancel
Save