virtualx-engine/doc/classes/ScrollBar.xml

<?xml version="1.0" encoding="UTF-8" ?>
<class name="ScrollBar" inherits="Range" category="Core" version="3.1">
	<brief_description>
		Base class for scroll bars.
	</brief_description>
	<description>
		Scrollbars are a [Range] based [Control], that display a draggable area (the size of the page). Horizontal ([HScrollBar]) and Vertical ([VScrollBar]) versions are available.
	</description>
	<tutorials>
	</tutorials>
	<demos>
	</demos>
	<methods>
	</methods>
	<members>
		<member name="custom_step" type="float" setter="set_custom_step" getter="get_custom_step">
		</member>
	</members>
	<signals>
		<signal name="scrolling">
			<description>
			</description>
		</signal>
	</signals>
	<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: Remove status from hardcoded version string It has no practical use case and just generates noise for each alpha, beta, etc. 2018-02-27 13:40:43 +01:00			`<class name="ScrollBar" inherits="Range" category="Core" version="3.1">`
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>`
			`Base class for scroll bars.`
			`</brief_description>`
			`<description>`
			`Scrollbars are a [Range] based [Control], that display a draggable area (the size of the page). Horizontal ([HScrollBar]) and Vertical ([VScrollBar]) versions are available.`
			`</description>`
			`<tutorials>`
			`</tutorials>`
			`<demos>`
			`</demos>`
			`<methods>`
			`</methods>`
			`<members>`
doc: Sync classref with current source [ci skip] 2017-09-13 08:49:40 +02:00			`<member name="custom_step" type="float" setter="set_custom_step" getter="get_custom_step">`
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			`</member>`
			`</members>`
			`<signals>`
			`<signal name="scrolling">`
			`<description>`
			`</description>`
			`</signal>`
			`</signals>`
			`<constants>`
			`</constants>`
			`</class>`