0

I have two nib files that use the same image, but I want to call the image nib_a_image.png when I reference it from nib a, and nib_b_image.png when I reference it from nib b.

The idea is that my designers could give me a new nib_a_image.png and only affect behavior of nib a.

But I don't want to increase the size of my app by including the image multiple times.

Would symlinks work? Sounds like symlinks would work. Not sure I love the idea.

Has anyone tried to do something like this?

funroll
  • 35,925
  • 7
  • 54
  • 59
  • If you could end up with two separate images later, why not simply use two now? Or simply use one and update the nib if needed in the future. – rmaddy Nov 10 '14 at 16:50
  • Have you tried it? It looks like they should work. http://stackoverflow.com/a/18085036/2708650 – Ian MacDonald Nov 10 '14 at 16:55
  • @rmaddy As I mentioned, I don't want to increase the size of my binary by embedding the same png twice. But more than that, I semantically want to know both are using the same image. – funroll Nov 10 '14 at 17:23
  • @IanMacDonald I've tried using symlinks before, and other people on my team yelled at me. Maybe because of Xcode bugs when working with symlinks. – funroll Nov 10 '14 at 17:24

0 Answers0