|
FAQ
Sept 22, 2023 15:26:45 GMT
Post by echo17 on Sept 22, 2023 15:26:45 GMT
Q: I'm having a problem, what is the best way to get help? A: answerQ: What is the difference between decoupler and Godot’s signals? A: answer
|
|
|
FAQ
Sept 26, 2023 9:23:43 GMT
Post by echo17 on Sept 26, 2023 9:23:43 GMT
Q: What is the difference between decoupler and Godot’s signals?
Godot’s signals are a great beginning to decoupling your code, but they have the limitation of needing to be connected directly to other nodes. Each signal must be attached to a specific node for that node to respond to the signal. This also means that every node that attaches to another node’s signals has to know about the other node, creating some dependencies. This gets especially problematic when working in teams or developing your code modularly as the other nodes might not be available for you to connect to.
decoupler, on the other hand, is a centralized messaging system. The only dependency a node needs is the decoupler object itself. events are broadcast to decoupler, not to specific nodes. decoupler then sends out the event to any registered listeners for that event. This means you can develop your project components modularly, not needing to worry about what nodes are connected to each other. You can also set up test nodes that listen to broadcasts to retrieve data before other parts of your system are fully operational.
Another advantage of decoupler is in requesting information from other nodes. signals cannot do this, since they are one-way.
|
|
|
FAQ
Oct 2, 2023 9:33:05 GMT
Post by echo17 on Oct 2, 2023 9:33:05 GMT
Q: I'm having a problem, what is the best way to get help?
Now and then you will come across a problem or question that may not be answered in these FAQs. If so, the best way to communicate the issue with me is to create a simple project that shows the problem occurring. Being able to dig into your project and run it against my source code is the quickest way for me to see what is going on.
Please include the invoice number you received when you purchased decoupler. I will only debug your projects if I can verify that you have purchased the plugin.
Note: You do not need to include the invoice attachment that you received, it is sufficient to just provide the invoice number if you prefer.
Be sure to keep your project simple. Try to eliminate anything else that is not relevant to the problem so that it is easier to narrow down the issue. Larger projects will take more time to sift through and may introduce other errors not directly related to decoupler. If possible, create a project from scratch that produces the issue you are seeing.
Also, be sure to include a list of steps that I can perform to reproduce the issue. Keep in mind that I have never seen your project before and do not know how to interact with it without your guidance. Let me know what you expect to see, since what I observe may appear operational to my uninitiated eye.
Note that the more complicated your example project or the less detail you provide in how to demonstrate an issue you are seeing, the lower the priority I will assign to helping you solve your issue. Most of my time is spent helping people with my various products, so to make it fair to everyone I will choose to help those that make it easier first.
When you create your project, just zip up the entire project folder. If you send me individual assets, the links between them will be lost and I will have to recreate the project from scratch. This can possibly produce skewed results since I have created a different project from the one you have sent. The best way to determine if your sample project is testable is to open it yourself and try to run it.
You can send your project to the email in my signature. I try to respond as quickly as possible (with the exception of weekends, holidays, and vacation time).
Note: Please DO NOT post your project on public forums!
|
|