Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - nathanm

Pages: [1]
1
Howdy,

After doing it wrong once, a while back (followed another dev's instructions instead of the NGUI readme instructions, plus using our asset server, which isn't real source control ... ) I really borked our project.

More recently, I followed the README upgrade steps and could successfully upgrade NGUI, except for one part: I use some control prefabs (examples/atlases/wooden) and atlases/fonts from that directory as well in creating some of my prefabs. 

After upgrading, all my prefabs need to be hand-edited to re-point them to the atlases/fonts.

Am I still upgrading wrong, or is this a known problem ?  If so, what would be the best way to prevent it ? (I'm considering: move/copy the NGUI examples directory to somewhere outside of the NGUI tree, so on delete it still exists. Or use our own fonts and atlases, but I haven't found an easy way to find all places I'm using something from those atlases/fonts - would rather not search by hand)

Steps I did:
1. In Unity, File -> New Scene
2. Delete the NGUI folder from the Project View.
2a. Check in the delete of NGUI to the asset server (if you delete and re-import w/o submitting the delete, the asset server can't figure it out and does bad things)
3. Import NGUI from the updated Unity Package.

Thanks!

Pages: [1]