UICamera Lateupdate change

[jlloyd]

Hello again,

We are trying out a change to UICamer Lateupdate.  We want to move the UIRoot.Broadcast("UpdateAnchors"); statement to after the onScreenResize(); call (line 1736ish).

This is changing the order of onScreenResize and UpdateAnchors. Previously, it called UpdateAnchors first then call onScreenResize. This could cause a problem if there are some UI Widget is using an UISretch object as anchors' target.

Usually onScreenResize won't be called on mobile devices except one situation: lock the android device when game running (I was using Sony Z1) and unlock it, you will receive two on ScreenResize call which the first one report change with portrait screen size then the second one with landscape screen size.

Do you see any issues with this change?

Thanks

Jobe

[ArenMook]

Why do you need to move the order of these two calls? NGUI only uses onScreenResize in two scripts, both legacy -- UIAnchor and UIStretch. Neither of these components should be used at this point. They're there for backwards compatibility only.

[Vicky]

It was because we didn't find another way to have a sprite extended width to match the width of the screen width other than using an UIStreth object as anchor target.

Do you have suggestion or example on what we can do for that requirement?

[ArenMook]

All widgets have built-in anchoring. To stretch a sprite, anchor its left and right points to the camera.

[Vicky]

Most of menu resources in out game were saved and used as prefabs. We create objects dynamically in game from those prefabs when we need to use them.

In this case, we have to manually assign the anchor targets every time when we create the object because the UICamera won't be packed in the prefab. And we might have multiply game object need to use UICamera as anchor. To simplify that operation, it's better create one game object which has the anchoring and everything else use it as reference. So we only need to assign UICamera to that one object.

Then this object has no different than UIStretch except we have to manually to setup UICamera for it.

As we still have UIStretch available I don't see why the way than another.

Can we just keep using UIStretch? With the suggest fixing mentioned in origin post?

[ArenMook]

If it works for what you're using, sure. Keep in mind though, you don't need to anchor to the camera. Anchoring to the panel has the same effect.