summaryrefslogtreecommitdiffstats
path: root/modules/nativescript/nativescript.h
Commit message (Collapse)AuthorAgeFilesLines
* merged gdnative and nativescript moduleKarroffel2017-09-031-325/+0
|
* Use HTTPS URL for Godot's website in the headersRémi Verschelde2017-08-271-1/+1
|
* Updated function argument namesWilson E. Alvarez2017-08-121-1/+1
|
* Forward frame call to GDNative librariesRuslan Mustakov2017-08-031-2/+10
|
* [NativeScript] call _init on instance creationKarroffel2017-07-271-0/+3
| | | | | This also adds basic locking for the set of owners to avoid threading problems
* Merge pull request #9882 from endragor/nativescript-refcountThomas Herzog2017-07-261-0/+3
|\ | | | | Forward refcount changes to NativeScriptInstance
| * Forward refcount changes to NativeScriptInstanceRuslan Mustakov2017-07-261-0/+3
| | | | | | | | | | | | This also changes Reference::unreference() to always invoke refcount_decremented. Previously it was not invoked until the count reached zero due to short-circuit evalution of boolean expressions.
* | Support multithreading for NativeScriptLanguageRuslan Mustakov2017-07-261-0/+28
|/ | | | | | | | | | | | | | Godot may call property setters from non-main thread when an object is loaded in the edtior. This means NativeScriptLanguage could be accessed from different threads, but it was not designed for thread-safety. Besides, previous behaviour made it so that godot_nativescript_init and godot_gdnative_init could be invoked from non-main thread, while godot_gdnative_thread is always invoked on the main thread. This may not be expected by the binding library. This commit defers native library initialization to the main thread and adds godot_nativescript_thread_enter and godot_nativescript_thread_exit callbacks to make a binding library aware of foreign threads.
* [NativeScript] fix double initialization in editorKarroffel2017-07-251-0/+2
|
* [NativeScript] forgot to uncomment userdata returnKarroffel2017-07-241-2/+2
|
* [GDNative] new GDNative APIKarroffel2017-07-241-0/+281
This adds GDNative as a separate class type. It can be used to interface with native libraries by using "native calls", which can be registered by modules (and in future other GDNative libraries?). It also reworks the currently called "GDNativeScript" into a "NativeScript" that just makes use of the new GDNative instead of it being the component that implements that functionality.