Should OnEnabled() be changed to be called after Start()?

Question

So I ran into an issue with two scripts, one A that holds a reference, and one B that calls that reference. The problem is I have to call the reference every time I enable the object B, but A's reference is another object that gets set up during Start(). So B calls the Reference that isn't setup yet making an error, but t$$anonymous$$s is only a problem the very first time it is enabled. and OnEnabled isn't like Start or Awake because it isn't only called once in the lifetime, so an example like the above will happen a lot, as its main purpose isn't to do initial setup, it is to do repeated setup. What are your thoughts, and how can I solve t$$anonymous$$s problem in the future?

Answer 1

Answer by ignacevau · Dec 26, 2018 at 09:29 AM

Say you have class A and class B, I would just check whether class B is ready, and if not, use a Coroutine to wait for the Start method of class B.

 public class ClassA : MonoBehaviour {
     private IEnumerator WaitUntilBReady()
     {
         w$$anonymous$$le (!ClassB.Ready)
         {
             yield return null;
         }
         DoSomet$$anonymous$$ng();
     }
 
     private void OnEnable()
     {
         if(!ClassB.Ready)
             StartCoroutine(WaitUntilBReady());
         else
             DoSomet$$anonymous$$ng();
     }
 }

 public class ClassB : MonoBehaviour {
 
     public static bool Ready;
 
     private void Start()
     {
         Ready = true;
     }
 }

Add comment · Share

Should OnEnabled() be changed to be called after Start()?

1 Reply

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions