asgardius/virtualx-engine
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
virtualx-engine/modules/gltf/doc_classes/GLTFState.xml

213 lines
5.6 KiB
XML
Raw Normal View History

doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<?xml version="1.0" encoding="UTF-8" ?>
<class name="GLTFState" inherits="Resource" version="4.0">
<brief_description>
</brief_description>
<description>
</description>
<tutorials>
</tutorials>
<methods>
<method name="get_accessors">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_animation_player">
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 15:28:05 +02:00
<return type="AnimationPlayer" />
<argument index="0" name="idx" type="int" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_animation_players_count">
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 15:28:05 +02:00
<return type="int" />
<argument index="0" name="idx" type="int" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_animations">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_buffer_views">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_cameras">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_images">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_lights">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_materials">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_meshes">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_nodes">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_scene_node">
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 15:28:05 +02:00
<return type="Node" />
<argument index="0" name="idx" type="int" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_skeleton_to_node">
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 15:28:05 +02:00
<return type="Dictionary" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_skeletons">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_skins">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="get_textures">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
doc: Sync classref with current source
2021-03-10 10:54:21 +01:00
<method name="get_unique_animation_names">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-03-10 10:54:21 +01:00
<description>
</description>
</method>
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<method name="get_unique_names">
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 15:28:05 +02:00
<return type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_accessors">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="accessors" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_animations">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="animations" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_buffer_views">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="buffer_views" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_cameras">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="cameras" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_images">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="images" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_lights">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="lights" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_materials">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="materials" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_meshes">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="meshes" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_nodes">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="nodes" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_skeleton_to_node">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="skeleton_to_node" type="Dictionary" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_skeletons">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="skeletons" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_skins">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="skins" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
<method name="set_textures">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="textures" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
doc: Sync classref with current source
2021-03-10 10:54:21 +01:00
<method name="set_unique_animation_names">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="unique_animation_names" type="Array" />
doc: Sync classref with current source
2021-03-10 10:54:21 +01:00
<description>
</description>
</method>
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<method name="set_unique_names">
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 15:28:05 +02:00
<return type="void" />
<argument index="0" name="unique_names" type="Array" />
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
<description>
</description>
</method>
</methods>
<members>
Better format arguments in variant parser
2019-09-24 19:45:03 +02:00
<member name="buffers" type="Array" setter="set_buffers" getter="get_buffers" default="[]">
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
</member>
Better format arguments in variant parser
2019-09-24 19:45:03 +02:00
<member name="glb_data" type="PackedByteArray" setter="set_glb_data" getter="get_glb_data" default="PackedByteArray()">
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
</member>
<member name="json" type="Dictionary" setter="set_json" getter="get_json" default="{}">
</member>
<member name="major_version" type="int" setter="set_major_version" getter="get_major_version" default="0">
</member>
<member name="minor_version" type="int" setter="set_minor_version" getter="get_minor_version" default="0">
</member>
Better format arguments in variant parser
2019-09-24 19:45:03 +02:00
<member name="root_nodes" type="Array" setter="set_root_nodes" getter="get_root_nodes" default="[]">
doc: Sync classref with current source
2021-01-04 14:33:44 +01:00
</member>
<member name="scene_name" type="String" setter="set_scene_name" getter="get_scene_name" default="&quot;&quot;">
</member>
<member name="use_named_skin_binds" type="bool" setter="set_use_named_skin_binds" getter="get_use_named_skin_binds" default="false">
</member>
</members>
</class>
Reference in a new issue Copy permalink