On Nov 26, 2016, at 12:04 PM, Quincey Morris wrote:
On Nov 26, 2016, at 09:06 , Carl Hoefs <
email@hidden> wrote:
Into which xcasset image well does one drop this magical 512x512 image? Every time I've tried using an image even 1 pixel off, Xcode would consider it an error and refuse to build my app. But if this works now, that's great!
I was talking about Mac icons, where there is an actual “512 pt” slot. If you’re talking about iOS, you might have to provide more than one icon, because there are multiple categories of icons, as well as sizes. If you’re only providing one icon in a category, you will have to provide it in a valid size (or 2x or 3x a valid size, depending on the category). If your complaint was that you can’t provide an icon in an *arbitrary* big-enough size and have Xcode scale it to a valid size, then, yes, you can’t do that. Sorry if I gave you false hope.
There's a lot going on here, so I'll give a little more info.
I was trying to take 4 images and apply them to the required slots within a launchimage image set within an xcassetlib for an iOS app.
WHAT USED TO HAPPEN was that when you selected one of the required slots for each icon, it would tell you the specifics about the image slot you selected AND it would display the expected dimensions (expected size) of the image that was supposed to go there.
This was nice. This was good. This told the programmer what the proper size of the image needed to be.
In Xcode 8.1, this is now gone.
Expected size and actual size of the images used is now missing.
This blows with regards to user experience. It takes an area that used to be straightforwards to use and makes it a pain in the ass.
The programmer should not have to waste 1/2 an hour getting their launch images to work.
Dragging 4 images into slots should take well less than a minute - even if the user makes mistakes.
The functionality needs to tell the user what the expected size of the image they need to use is and what the size of the image they are using is.
The subtext under the image slot used to display this information and the inspector panel on the right also used to provide this information.
Hell, even put a red X treatment next to the subtext if there isn't a match.
It worked before in Xcode7.3.x) It's a pain in the ass now. (8.1).
I hope this explains the issue more clearly.