You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If u have a very big lag, insTime can be more than insDelay and also more than insEndDelay before ever going into the first if, which means changeBegan will never become true, and therefore, changeComplete will never be called
You can easily repro this by putting a break point on the first if check, and after a few seconds (more than the insEndDelay) break again
U will see that insTime will be outside of the first if, but changeBegan is still false
A possible solution would be to change the first if to:
The issue is in this piece of code:
If u have a very big lag, insTime can be more than insDelay and also more than insEndDelay before ever going into the first if, which means changeBegan will never become true, and therefore, changeComplete will never be called
You can easily repro this by putting a break point on the first if check, and after a few seconds (more than the insEndDelay) break again
U will see that insTime will be outside of the first if, but changeBegan is still false
A possible solution would be to change the first if to:
if (insTime > insDelay && (!instance.changeBegan || insTime < insEndDelay) {
The text was updated successfully, but these errors were encountered: