virtualx-engine/doc/classes/VSeparator.xml

<?xml version="1.0" encoding="UTF-8" ?>
<class name="VSeparator" inherits="Separator" version="4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="../class.xsd">
	<brief_description>
		Vertical version of [Separator].
	</brief_description>
	<description>
		Vertical version of [Separator]. Even though it looks vertical, it is used to separate objects horizontally.
	</description>
	<tutorials>
	</tutorials>
	<theme_items>
		<theme_item name="separation" data_type="constant" type="int" default="4">
			The width of the area covered by the separator. Effectively works like a minimum width.
		</theme_item>
		<theme_item name="separator" data_type="style" type="StyleBox">
			The style for the separator line. Works best with [StyleBoxLine] (remember to enable [member StyleBoxLine.vertical]).
		</theme_item>
	</theme_items>
</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-02-14 14:18:53 +01:00			`<class name="VSeparator" inherits="Separator" 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-12 22:42:36 +02:00			`<brief_description>`
			`Vertical version of [Separator].`
			`</brief_description>`
			`<description>`
Proofread and improve the whole class reference - Document a few more properties and methods - Add more information to many classes - Fix lots of typos and gramar mistakes - Use [code] tags for parameters consistently - Use [b] and [i] tags consistently - Put "Warning:" and "Note:" on their own line to be more visible, and make them always bold - Tweak formatting in code examples to be more readable - Use double quotes consistently - Add more links to third-party technologies 2019-06-22 01:04:47 +02:00			`Vertical version of [Separator]. Even though it looks vertical, it is used to separate objects horizontally.`
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>`
			`<theme_items>`
Add theme item descriptions to the online documentation 2021-08-04 18:54:41 +02:00			`<theme_item name="separation" data_type="constant" type="int" default="4">`
Add LOTS of missing docs 2020-03-03 19:21:21 +01:00			`The width of the area covered by the separator. Effectively works like a minimum width.`
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			`</theme_item>`
Add theme item descriptions to the online documentation 2021-08-04 18:54:41 +02:00			`<theme_item name="separator" data_type="style" type="StyleBox">`
Add LOTS of missing docs 2020-03-03 19:21:21 +01:00			`The style for the separator line. Works best with [StyleBoxLine] (remember to enable [member StyleBoxLine.vertical]).`
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			`</theme_item>`
			`</theme_items>`
			`</class>`