Author Topic: Updating, but when using some of the example/sample prefabs  (Read 1293 times)


  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 1
    • View Profile
Updating, but when using some of the example/sample prefabs
« on: December 05, 2014, 10:21:28 AM »

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.



  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Updating, but when using some of the example/sample prefabs
« Reply #1 on: December 05, 2014, 04:08:29 PM »
All references are kept, unless you broke them in the past. Copying NGUI's files from one project to another without including the metadata will break it, for example. Once it's broken, you're pretty screwed. Either NGUI's examples and prefabs will be broken, or your own. You can't fix both without quite a bit of re-linking on your part which is long and tedious.