-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is no initialize button #65
Comments
Hm, ok. I'll have to look into why that's happening. Thanks for letting me know. And yeah, I think increasing the usability by having the CallbackDelegator and Behavior have a more explicit relationship that is just overrideable might be a good idea. I mean, I want users to be able to create and use their own base Behavior class, but that doesn't mean we can't make things easier for new users. |
ok cool another thing I would like to see would be allowing existing nodes like I don't really see how the current system can work due to godot forcing people to have a certain hierarchy. |
This is fundamentally impossible without changing the core of Godot Engine's entire Object-Script relationship. That will probably never happen, and I certainly have no intention of maintaining a hard fork of Godot.
Well, you can still use it the same way you would use any has-a relationship in programming, so I'm not quite sure what you mean. You can't use CallbackDelegator/Behavior as a replacement for a Spatial or Node2D as a root node or something, but if you have utility / game logic in your application that you want to attach to a node tree, it may be good option for that use case over simply attaching many child nodes to provide those same utilities. |
I came here from this video
however there is no initialize button like in the video and I get a error when I click on the base type box
I am using godot 3.2.1 btw
The text was updated successfully, but these errors were encountered: