-
Notifications
You must be signed in to change notification settings - Fork 13
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
Error when get a property of a node #42
Comments
It seems that it is treated as a resource rather than a node |
Hmm. I probably broke this with some recent changes to accommodate some unusual situations. You could try 1.1.6 until I can fix it. |
Well, 1.1.6 works fine on this issue. Thanks. |
Once "scene unique nodes" (which does looks nice) is in a stable release, it does seem to overlap what OnReadyFind can do, although not quite all. It would also require changing code to start using it, and I don't see the reason to force people to do that by removing OnReadyFind. I'm just waiting to see if GodotOnReady is necessary in 4.0 and either rewrite to fit or drop it entirely. 😄 GodotOnReady as a whole should be obsolete in 4.0, since this issue's milestone is set: |
Thanks for the details. |
I've fixed this up and released GodotOnReady 1.2.1. (But, OnReadyFind is the only thing that's been added since 1.1.6, so no need to upgrade if you aren't planning on using it. 😄.) Thanks for noticing and filing the issue! |
1.2.1 works fine. |
The text was updated successfully, but these errors were encountered: