The best workflow we have is to remove all images and re-add them, then manually set the metadata again, or handle all slicing and tiling in code, negating the benefit of using an asset catalog. There’s no easy way to replace images in an asset catalog while maintaining slicing, tiling and other metadata. That means it’s common for us to have 100s or 1000s of images to update. We automate our asset exporting as much as possible, and image files are treated as ephemeral - our build process for images typically rebuilds the entire set. Use them.ĭragging in a file called icon-120.png into an app icon asset catalog twice duplicates the file, with the handy filename of icon-121.png.
Xcode knows the image dimensions required, and it knows the image dimensions of the files I’m dragging in. I really think asset catalogs should be smarter and provide easier ways to batch add files. There’s 42 different image sizes required for watchOS Complications. In cases where icon sizes are the same and an identical image is likely being used (iPhone home and iPhone spotlight are both 120px), dragging the same image twice into the asset catalog results in duplicate files. That’s 19 separate actions to drag in the 14 different iOS app icon sizes (if you’re careful with file names and select all the pixel densities at once, you can reduce this a bit). For app icons, each size needs to be dragged in one by one. That’s perfectly reasonable in some scenarios, but it does require one drag per asset catalog. Images can be batch added to an asset catalog by dragging them into Xcode. This is largely due to the format used for asset catalogs and Xcode’s behaviour. However, in practice asset catalogs have made common tasks slower and more difficult, reduced our ability to automate design integration, and increased the chance of errors. It makes sense to group images and metadata together, with a visual way to edit it all in Xcode.
0 kommentar(er)
