virtualx-engine/modules/visual_script/doc_classes/VisualScriptSelf.xml

<?xml version="1.0" encoding="UTF-8" ?>
<class name="VisualScriptSelf" inherits="VisualScriptNode" version="3.2">
	<brief_description>
		Outputs a reference to the current instance.
	</brief_description>
	<description>
		Provides a reference to the node running the visual script.
		[b]Input Ports:[/b]
		none
		[b]Output Ports:[/b]
		- Data (object): [code]instance[/code]
	</description>
	<tutorials>
	</tutorials>
	<methods>
	</methods>
	<constants>
	</constants>
</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-12 22:42:36 +02:00			`<?xml version="1.0" encoding="UTF-8" ?>`
doc: Drop unused 'category' property from header We already removed it from the online docs with #35132. Currently it can only be "Built-In Types" (Variant types) or "Core" (everything else), which is of limited use. We might also want to consider dropping it from `ClassDB` altogether in Godot 4.0. 2020-01-26 16:01:49 +01:00			`<class name="VisualScriptSelf" inherits="VisualScriptNode" version="3.2">`
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-12 22:42:36 +02:00			`<brief_description>`
[DOCS] Update 12 VisualScript* nodes 2017-10-15 05:11:00 +02:00			`Outputs a reference to the current instance.`
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-12 22:42:36 +02:00			`</brief_description>`
			`<description>`
[DOCS] Update 12 VisualScript* nodes 2017-10-15 05:11:00 +02:00			`Provides a reference to the node running the visual script.`
			`[b]Input Ports:[/b]`
			`none`
			`[b]Output Ports:[/b]`
			`- Data (object): [code]instance[/code]`
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-12 22:42:36 +02:00			`</description>`
			`<tutorials>`
			`</tutorials>`
			`<methods>`
			`</methods>`
			`<constants>`
			`</constants>`
			`</class>`