koobas.hobune.stream
Events vs Normal Functions
Doesn't matter how much I strive to understand the usefullness of events, I simply can't see how they differs from normal Functions.
Let's suppose that I need to check if a ball Object has or not touched the floor. Without using events, I'd check at every update() if the ball position in y-axys is the same as the floor. If it is, a function will be called in which something happens.
So what are events useful for ? To do the same with events I need to create-an-istance-of-a-delegate-and-pass-it-in-the-declaration-of-an-event-that-will-then-define-a-method-which-will-be-triggered-if-something-in-different-assembly-as-been-subscribed-to-the-said-event-declaration-to-trigger-the-function-in-the-other-assembly-whaaat ?!
I'd need to do all of this to actually change the function in Update() with an event ? Or pheraps i'm completely wrong and events may be triggered in this scenario even without the use of the update() function ? I mean i'd see the great use of events if in this case for example it would ignite without having to check everytime the y-axys of both objects but it is not the case (as far as I understood)
I find my self always relying to update() if I need to do particular behaviour in case somethings happens, is it wrong ? Because generally I end up checking for loads of information alltogheter in the same frame to understand if I should raise some methods or not, is this wrong ?
What part of events I'm not understanding right ?
I don't understand how you are trying to use events. Here's how I might use it in Unity. Imagine a game where a team scored when the ball goes into a goal. The goal could fire of a 'score' event. Different scripts on different objects would receive this event. Other than to make sure not to cause a null reference, the goal does not need to know what objects need this event. The scoreboard would get the event and increment the score. The ball would get this event and return to the starting position. The audio manager would get this event and play a sound. The players get this event and return to their starting position...etc. Only the goal understands the criteria for a score. Each individual script/object handles its own behavior when a score is made.
Without events, the code would be uglier and less-maintainable. You might have a slow, send message solution, or you might have to statically define the list of scripts that need to be informed in the goal object, or each object might have to query the goal each frame to see if a goal is made, or...
Specifically about "or each object might have to query the goal each frame to see if a goal is made" how do events avoid this ? Can't I subscribe the script with the function to each object ? why events would be more helpfull ? I'm sorry If I cannot explain better why things are not very clear to me
"how do events avoid this"
Each object that listens for an event has a method that is only called when the event is fired (by the goal in my example above).
Read this answer:
http://answers.unity3d.com/questions/600416/how-do-delegates-and-events-work.html
Watch the video at the 'YoutubeVideo' link in that answer.
