Timeline for How can I avoid tight script coupling in Unity?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 13, 2015 at 4:20 | comment | added | Matthew Pigram | I also believe that there are some plugins available in the unity asset store that can expose interfaces and other programming constructs not supported by the Unity Inspector, it might be worth having a quick search. | |
| Feb 12, 2015 at 19:11 | comment | added | Brett Satoru | I'm a personal fan of the use of events and delegates where Component objects know about the more internal core systems but the core systems don't know anything about the component pieces. But I wasn't one hundred percent sure that was the way they wanted their answer designed. So I went with something that answered how to get scripts uncoupled completely. | |
| Feb 12, 2015 at 19:01 | comment | added | jhocking | SendMessage() does address this situation and I use that command in many situations, but an untargeted message system like this is less efficient than directly having a reference to the receiver. You should be careful of relying on this command for all routine communication between objects. | |
| Feb 12, 2015 at 18:57 | review | First posts | |||
| Feb 12, 2015 at 19:30 | |||||
| Feb 12, 2015 at 18:54 | history | answered | Brett Satoru | CC BY-SA 3.0 |