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:
@ -89,10 +89,6 @@ void VisibleOnScreenNotifier3D::_bind_methods() {
|
||||
ADD_SIGNAL(MethodInfo("screen_exited"));
|
||||
}
|
||||
|
||||
Vector<Face3> VisibleOnScreenNotifier3D::get_faces(uint32_t p_usage_flags) const {
|
||||
return Vector<Face3>();
|
||||
}
|
||||
|
||||
VisibleOnScreenNotifier3D::VisibleOnScreenNotifier3D() {
|
||||
RID notifier = RS::get_singleton()->visibility_notifier_create();
|
||||
RS::get_singleton()->visibility_notifier_set_aabb(notifier, aabb);
|
||||
|
||||
Reference in New Issue
Block a user