godot/doc/classes/RemoteTransform3D.xml

<?xml version="1.0" encoding="UTF-8" ?>
<class name="RemoteTransform3D" inherits="Node3D" version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../class.xsd">
	<brief_description>
		RemoteTransform3D pushes its own [Transform3D] to another [Node3D] derived Node in the scene.
	</brief_description>
	<description>
		RemoteTransform3D pushes its own [Transform3D] to another [Node3D] derived Node (called the remote node) in the scene.
		It can be set to update another Node's position, rotation and/or scale. It can use either global or local coordinates.
	</description>
	<tutorials>
	</tutorials>
	<methods>
		<method name="force_update_cache">
			<return type="void" />
			<description>
				[RemoteTransform3D] caches the remote node. It may not notice if the remote node disappears; [method force_update_cache] forces it to update the cache again.
			</description>
		</method>
	</methods>
	<members>
		<member name="remote_path" type="NodePath" setter="set_remote_node" getter="get_remote_node" default="NodePath(&quot;&quot;)">
			The [NodePath] to the remote node, relative to the RemoteTransform3D's position in the scene.
		</member>
		<member name="update_position" type="bool" setter="set_update_position" getter="get_update_position" default="true">
			If [code]true[/code], the remote node's position is updated.
		</member>
		<member name="update_rotation" type="bool" setter="set_update_rotation" getter="get_update_rotation" default="true">
			If [code]true[/code], the remote node's rotation is updated.
		</member>
		<member name="update_scale" type="bool" setter="set_update_scale" getter="get_update_scale" default="true">
			If [code]true[/code], the remote node's scale is updated.
		</member>
		<member name="use_global_coordinates" type="bool" setter="set_use_global_coordinates" getter="get_use_global_coordinates" default="true">
			If [code]true[/code], global coordinates are used. If [code]false[/code], local coordinates are used.
		</member>
	</members>
</class>
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`<?xml version="1.0" encoding="UTF-8" ?>`
Add an XML schema for documentation This makes it easier to spot syntax errors when editing the class reference. The schema is referenced locally so validation can still work offline. Each class XML's schema conformance is also checked on GitHub Actions. 2022-02-14 21:18:53 +08:00			`<class name="RemoteTransform3D" inherits="Node3D" version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../class.xsd">`
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`<brief_description>`
Update documentation for Transform3D 2020-05-03 16:27:36 +08:00			`RemoteTransform3D pushes its own [Transform3D] to another [Node3D] derived Node in the scene.`
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`</brief_description>`
			`<description>`
Update documentation for Transform3D 2020-05-03 16:27:36 +08:00			`RemoteTransform3D pushes its own [Transform3D] to another [Node3D] derived Node (called the remote node) in the scene.`
Clarify which direction RemoteTransform[2D] work 2018-09-10 21:54:32 +08:00			`It can be set to update another Node's position, rotation and/or scale. It can use either global or local coordinates.`
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`</description>`
			`<tutorials>`
			`</tutorials>`
			`<methods>`
Added force_update_cache() to RemoteTransform and RemoteTransform2D 2019-07-04 06:17:05 +08:00			`<method name="force_update_cache">`
doc: Use self-closing tags for `return` and `argument` For the time being we don't support writing a description for those, preferring having all details in the method's description. Using self-closing tags saves half the lines, and prevents contributors from thinking that they should write the argument or return documentation there. 2021-07-30 21:28:05 +08:00			`<return type="void" />`
Added force_update_cache() to RemoteTransform and RemoteTransform2D 2019-07-04 06:17:05 +08:00			`<description>`
doc: Update classref with node renames A few extra renames for classes which were missed in last week's PRs. 2020-03-31 00:22:57 +08:00			`[RemoteTransform3D] caches the remote node. It may not notice if the remote node disappears; [method force_update_cache] forces it to update the cache again.`
Added force_update_cache() to RemoteTransform and RemoteTransform2D 2019-07-04 06:17:05 +08:00			`</description>`
			`</method>`
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`</methods>`
			`<members>`
doc: Add default values to all properties Thanks to @bojidar-bg's impressive work in #29380. 2019-06-29 18:38:01 +08:00			`<member name="remote_path" type="NodePath" setter="set_remote_node" getter="get_remote_node" default="NodePath("")">`
doc: Update classref with node renames A few extra renames for classes which were missed in last week's PRs. 2020-03-31 00:22:57 +08:00			`The [NodePath] to the remote node, relative to the RemoteTransform3D's position in the scene.`
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`</member>`
doc: Add default values to all properties Thanks to @bojidar-bg's impressive work in #29380. 2019-06-29 18:38:01 +08:00			`<member name="update_position" type="bool" setter="set_update_position" getter="get_update_position" default="true">`
doc: Remove hardcoded default values from descriptions They are now generated automatically by doctool. 2019-06-29 21:24:23 +08:00			`If [code]true[/code], the remote node's position is updated.`
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`</member>`
doc: Add default values to all properties Thanks to @bojidar-bg's impressive work in #29380. 2019-06-29 18:38:01 +08:00			`<member name="update_rotation" type="bool" setter="set_update_rotation" getter="get_update_rotation" default="true">`
doc: Remove hardcoded default values from descriptions They are now generated automatically by doctool. 2019-06-29 21:24:23 +08:00			`If [code]true[/code], the remote node's rotation is updated.`
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`</member>`
doc: Add default values to all properties Thanks to @bojidar-bg's impressive work in #29380. 2019-06-29 18:38:01 +08:00			`<member name="update_scale" type="bool" setter="set_update_scale" getter="get_update_scale" default="true">`
doc: Remove hardcoded default values from descriptions They are now generated automatically by doctool. 2019-06-29 21:24:23 +08:00			`If [code]true[/code], the remote node's scale is updated.`
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`</member>`
doc: Add default values to all properties Thanks to @bojidar-bg's impressive work in #29380. 2019-06-29 18:38:01 +08:00			`<member name="use_global_coordinates" type="bool" setter="set_use_global_coordinates" getter="get_use_global_coordinates" default="true">`
doc: Remove hardcoded default values from descriptions They are now generated automatically by doctool. 2019-06-29 21:24:23 +08:00			`If [code]true[/code], global coordinates are used. If [code]false[/code], local coordinates are used.`
Changed the doc class generation to individual files per class. It is also possible to save module files in module directories and the build system will recognize them. 2017-09-13 04:42:36 +08:00			`</member>`
			`</members>`
			`</class>`