On Mar 21, 2012, at 6:21 PM, G S wrote: On Wed, Mar 21, 2012 at 2:56 PM, M Pulis <email@hidden> wrote:
Could be my eyes....
Your Xcode icons for Default.png and email@hidden look the same, while the icons for icon.png and icon2x.png look different. I would check the file type of icon.png to be sure.
You're right about the display, but that's just Xcode randomly showing a thumbnail for the low-res one and a generic "file" icon for the Retina one. If you click on the Retina one, though, it shows up just fine in the editor pane.
And, even more random: If I let Xcode do this copying that it wants to do, it sure enough makes redundant icon files in the project root directory. But if I then delete these from the project and move them to the trash, the Retina icon STAYS in the image well, and "Show in Finder" shows the correct one in the Resources directory! The image well for the low-res icon gets cleared out and continues to complain. So the one you noted as missing its thumbnail is the one that I can cajole into working properly.
How does that match up with the info for the file showed in the Utilities panel File Inspector, under Identity and Type?
It should be all the way at the top right. I guess we're all programmers here: How does this bug persist? This pisses me off. Now I'm messing up my project's file organization to work around a pathetically elementary bug.
Don't feel bad, I organized a merged project from two developers, then went back to working on a fork of the original and have to do it all over again. A boatload of files at the top level of the project, a boatload within the folder name that has the same name as the project ala Xcode 4's glorious nesting.
Xcode 4 needs a "make things stupid simple like Xcode 3" mode.
Director had this problem many years ago. Our user surveys said that the product was too complex for new users. So management decreed that we add a lot of "ease of use features". I strongly mentioned that we need a MODE where the GUI is set to simple and all the other more complex parts are able to be enabled as needed so that users can enable features as they feel the need to do so. Nope. What happened was that all the ease of use features were lumped in with the rest of the product and all were enabled all the time - right next to the features that were deemed too complicated for new users, creating a more complicated product that was harder to understand.
Yeah. Way to bloat a product. We got that down right.
|