Closed frankiezafe closed 6 years ago
it's weird, I thought I merged this PR already.... as for the standalone receiver (or sender), I actually had one at some point with property bindings. As I was struggling with a race condition (due to the threading, indeed) I went back to the current state with an idea of making the UI with GDscript to control it. I am actually not sure about which way I would prefer. In fact, another decision to be made is whether gdosc should be ported to GDNative. When I started working on it, GDnative was still in flux so I didn't bother. I postponed all these questions for later. I am open to discuss the merits of these.
Hello,
Here is a proposal to create a "standalone" object to receive messages. It is working but not yet sending messages back to the engine.
The object is configurable without gdscript, via the UI
The object can autostart when the game starts and stops when it quit, thanks to the _notification() method.
If you're ok with this kind of architecture, i can do something similar for the sender (should a bit easier as there is no thread involved).