-
-
Notifications
You must be signed in to change notification settings - Fork 21.1k
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
Fix inconsistent last_modified_time
handling in GDExtension
#82603
Conversation
Tested locally on Windows 10 - now reload is activated only if original DLL is really changed. |
@dsnopek FYI |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, good catch! I definitely need to (re-)test on Windows more often in general.
I tried your PR on Windows 10 and it works great! I also tested on Linux just to make sure there aren't any non-Windows regressions, and it's also all good there.
Ah, and we don't generally put issue numbers in commit messages. It'd probably be good to amend the commit message to match the PR title, which is more like the standard used for commit messages in Godot - the production team will like that better :-) |
…oad spam on Windows 10)
ea3c812
to
43f92e4
Compare
last_modified_time
handling (prevent GDExtension reload spam on Windows 10)
last_modified_time
handling (prevent GDExtension reload spam on Windows 10)last_modified_time
handling in GDExtension
Thanks! And congrats for your first merged Godot contribution 🎉 |
yeah, that's fun to be part of :) |
Fixes #82601 fix inconsistent last_modified_time handling. GDExtension::library_path variable stores original DLL path now.