Inset widget with dynamic height weird drifting position bugs

[Tiktaalik]

I'm trying to build an inset widget (let's call it InsetWidget) much like what is described on the UIRect documentation, but designed such that the inner widget is a UILabel that resizes its height based on the text. As the inset UILabel expands, the outer containing UIWidget should also expand.

I've been able to create this by having the UILabel not anchor its bottom, and having the containing UIWidget anchor its bottom to the bottom of the inset UILabel.

Unfortunately I'm getting very weird bugs where this InsetWidget's height is drifting slowly larger. I've also on re-running seen an issue where the height of the UILabel was going back and forth between a negative and positive value, causing the whole thing to wobble.

Is this a legitimate way to build this sort of Widget or will doing this always lead to problems?

(As well these widgets are being added to a UITable if that means anything. I haven't yet tested how this runs outside of that situation)

Running NGUI 3.5.5

[ArenMook]

1. Update your NGUI. Because... bug fixes.
2. Make a label -- ALT+SHIFT+L. Set it to resize freely instead of shrink content.
3. Add a child sprite to it -- ALT+SHIFT+S, change its depth to be label's depth -1. Resize it to cover the label as you want it to be.
4. Enable Unified anchoring on the sprite. It will automatically anchor to the label.
5. Now select the label and type something. The sprite will resize automatically.

[Tiktaalik]

Ok that worked thanks.

I'd love to upgrade NGUI, but we're in the thick of things at the moment and I'm really not able to risk having some sort of compatibility problem.

It's a shame that Unity doesn't have a better upgrade system that would allow you to roll back in case something goes wrong.

[ArenMook]

Unity doesn't need it. You can easily set up a git repository and revert back if something goes wrong. There is no reason to work without a repository set up, regardless of what you're doing.

[Tiktaalik]

Of course you're right. We have source control so we could easily roll back.