Discern between virtual and abstract class bindings
* Previous "virtual" classes (which can't be instantiated) are not corretly named "abstract". * Added a new "virtual" category for classes, they can't be instantiated from the editor, but can be inherited from script and extensions. * Converted a large amount of classes from "abstract" to "virtual" where it makes sense. Most classes that make sense have been converted. Missing: * Physics servers * VideoStream * Script* classes. which will go in a separate PR due to the complexity involved.
This commit is contained in:
parent
741bbb9d7c
commit
6f51eca1e3
90 changed files with 1075 additions and 272 deletions
|
|
@ -39,10 +39,6 @@ AABB CPUParticles3D::get_aabb() const {
|
|||
return AABB();
|
||||
}
|
||||
|
||||
Vector<Face3> CPUParticles3D::get_faces(uint32_t p_usage_particle_flags) const {
|
||||
return Vector<Face3>();
|
||||
}
|
||||
|
||||
void CPUParticles3D::set_emitting(bool p_emitting) {
|
||||
if (emitting == p_emitting) {
|
||||
return;
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue