Corrects usage of 'is' instead of 'extends' for testing node inheritance.
This commit is contained in:
parent
5c3f05a680
commit
61572a57e9
1 changed files with 1 additions and 1 deletions
|
@ -14062,7 +14062,7 @@
|
||||||
<description>
|
<description>
|
||||||
Add a custom type, which will appear in the list of nodes or resources. An icon can be optionally passed.
|
Add a custom type, which will appear in the list of nodes or resources. An icon can be optionally passed.
|
||||||
When given node or resource is selected, the base type will be instanced (ie, "Spatial", "Control", "Resource"), then the script will be loaded and set to this object.
|
When given node or resource is selected, the base type will be instanced (ie, "Spatial", "Control", "Resource"), then the script will be loaded and set to this object.
|
||||||
You can use the [method EditorPlugin.handles] to check if your custom object is being edited by checking the script or using 'extends' keyword.
|
You can use the [method EditorPlugin.handles] to check if your custom object is being edited by checking the script or using 'is' keyword.
|
||||||
During run-time, this will be a simple object with a script so this function does not need to be called then.
|
During run-time, this will be a simple object with a script so this function does not need to be called then.
|
||||||
</description>
|
</description>
|
||||||
</method>
|
</method>
|
||||||
|
|
Loading…
Reference in a new issue