Updating from 2.1.6 to latest

[pgeorges]

Hey Michael,

First and foremost, thank you for the great work you've done on NGUI!

Now, I've been given a mandate to transform a client's UI into something that will work with controller setup. I thought the easiest would be to update to a recent version of NGUI and make use of the UIKeyNavigation component. Then I realized that the version of NGUI being used in the client's project is 2.1.6. Lemme tell you that when I replaced the old code with 3.5.5, things pretty much exploded. Event handling, class names, API for buttons, everything is pretty much blown.

Do you have any suggestions?

Thank you!

Paul

[ArenMook]

Ouch. I suggest first, update to 2.7.0, and only then proceed to go up to NGUI 3 using the upgrade tools to ease the process. 2.1.6 is uber old though, so I suspect you will run into quite a few issues. Be sure to drag every prefab into the scene to have the auto-update logic kick in, then Apply the changes.

[pgeorges]

Thanks for the suggestion Michael! Yeah, everything from NGUITools to event handling to class name differences and API changes. I feel like I'm kind of screwed haha.

Given that I have to fix event handling (I have to get rid of all the references to UIEvents), what do you suggest as a best practice? Custom delegates alongside UIEventListener? UIEventTrigger?

Also, when using the tool for updating 2.7.0 to 3.x.x, do you suggest overwriting the entire library and then running the tool? Is it best to unpack the tool first so that it can compile and then to overwrite the library?

Cheers!

[ArenMook]

Overwriting the library? Not sure what you mean. The upgrade tools re-adds some removed classes (like UISlicedSprite) and gives you the ability to auto-upgrade those older classes into the UISprite.

I'm also not sure what you mean by UIEvents. UIEventListener is still there. UIButtonMessage as well. Button message is a legacy component that can be replaced with the Event Trigger, but you can keep using it if you like.