Interface Builder refuses to see "@2x" image files - AGAIN in 5.0

Question

This was a problem in Xcode 4.0. Eventually, it was fixed.
Now that Xcode 5.0 is out, it's back to the same problem. And, Xcode 5.0 asks you to convert your XIB files to the new format, so it can screw you up without you even knowing it!
PROBLEM:
The @2x images are NOT visible in interface builder. It cannot be selected from the list. It shows an unknown image (question mark) if you manually type it in...which renders layout design pointless if you need those @2x files.
Many, many, many developers reuse the @2x images in the iPad xib files. Now, all of the images will either be shrunk or stretched from lower-res images...because it REMOVES the @2x extension for any images it finds in a xib file.
SUGGESTIONS in the past:
- Copy your @2x images to ~ipad images, because the framework will automatically use it.
NO. I don't need to up the size of my app significantly with duplicate images.
- Rename the @2x images to something else (e.g. -2x).
NO. Because the framework will no longer auto load them for iPhone retina.
- Just manually name them with the @2x and live with the broken image in IB.
NO. Because most people actually care about the layout.
- Create a separate iPad app.
NO. Because customers shouldn't have to pay twice for the same app for 2 different devices.
- Programmatically change the images to @2x if it's an iPad.
UGH. This is what I've ended up doing, but how ridiculous is that?
Anyone else found a way around this?

Answer 1

  NSString* path = [[NSBundle mainBundle] pathForResource:@"imageName" ofType:@"png"];
          NSData* data = path ? [NSData dataWithContentsOfFile:path] : nil;
          UIImage* img = data ? [UIImage imageWithData:data] : nil;
  if( img ) [button setImage:img forState:UIControlStateNormal];
OR
  NSString* path = [[NSBundle mainBundle] pathForResource:@"imageName" ofType:@"png"];
  UIImage* img = [UIImage imageWithContentsOfFile:path];
  if( img ) [button setImage:img forState:UIControlStateNormal];
Both should bypass auto-scaling.