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

<?xml version="1.0" encoding="UTF-8" ?>
<class name="VisualScriptIterator" inherits="VisualScriptNode" version="3.5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../doc/class.xsd">
	<brief_description>
		Steps through items in a given input.
	</brief_description>
	<description>
		This node steps through each item in a given input. Input can be any sequence data type, such as an [Array] or [String]. When each item has been processed, execution passed out the [code]exit[/code] Sequence port.
		[b]Input Ports:[/b]
		- Sequence: [code]for (elem) in (input)[/code]
		- Data (variant): [code]input[/code]
		[b]Output Ports:[/b]
		- Sequence: [code]each[/code]
		- Sequence: [code]exit[/code]
		- Data (variant): [code]elem[/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" ?>`
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-03-16 23:01:02 +01:00			`<class name="VisualScriptIterator" inherits="VisualScriptNode" version="3.5" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../../../doc/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-12 22:42:36 +02:00			`<brief_description>`
[DOCS] Update 12 VisualScript* nodes 2017-10-15 05:11:00 +02:00			`Steps through items in a given input.`
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			`This node steps through each item in a given input. Input can be any sequence data type, such as an [Array] or [String]. When each item has been processed, execution passed out the [code]exit[/code] Sequence port.`
			`[b]Input Ports:[/b]`
			`- Sequence: [code]for (elem) in (input)[/code]`
			`- Data (variant): [code]input[/code]`
			`[b]Output Ports:[/b]`
			`- Sequence: [code]each[/code]`
			`- Sequence: [code]exit[/code]`
			`- Data (variant): [code]elem[/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>`