Panel not rendering after animation

[boofcpw]

Hey,

I have some panels that are instantiated and have animations played (translation and alpha 0-1) as part of a window management system.

Everything works fine the first time, and the panel is created, and animated in. Animation out also works fine.

However when the panel is activated again and the animation plays, the panel remains invisible.

The animation plays correctly, and the panel alpha is animated to 1 and the transform is moved, but nothing is drawn.

Upon changing any property of the panel (nudging the alpha for example) , it becomes visible and everything works as expected.

There are no draw calls present, despite the pane and every widget below it being turned on.

Any help here would be great thanks

[badawe]

I have this problem here too, since this last 3.7.1 update.

Lets hope the new update come out soon, and fix this issue.

[ArenMook]

As I've mentioned it many times before, you can't animate private variables. "MAlpha" is a private variable, and the fact that Unity shows it is a bug in Unity. NGUI works through properties, not variables. UIRect.alpha is what you should be animating. To do it via a Unity animation, you need an intermediate script.

1. using UnityEngine;
2.  
3. [ExecuteInEditMode]
4. [RequireComponent(typeof(UIRect))]
5. public class AlphaAnimator : MonoBehaviour
6. {
7.     [Range(0f, 1f)]
8.     public float alpha = 1f;
9.  
10.     void Update () { GetComponent<UIRect>().alpha = alpha; }
11. }

[boofcpw]

Thanks for that.

[badawe]

Hey @ArenaMook let me get this straight.

You should not animate a alpha from a panel? Never?! 

Sorry about this, but I've never read this before! hahah If I use one Widget as a root of all other objects, and change this alpha instead, this will work fine right?

[ArenMook]

You can animate alpha just fine, but you need to use an intermediate class like I mentioned above.

You should not animate private variables, as Unity doesn't have a notification that says "hey, animation just changed your values, you might want to do something!", so there is no way to know when animation alters something without saving previous values and checking for inequality every update, which is obviously way too much overhead.