I’m using a whole bunch of CALayers, creating a tile-based image not unlike GoogleMaps (different versions of the same image with more/less detail).
The code I’m using to do this is:
UIImage* image = [self loadImage:obj.fileName zoomLevel:obj.zoomLevel]; [CATransaction setValue:(id)kCFBooleanTrue forKey:kCATransactionDisableActions]; obj.layerToAddTo.contents = [image CGImage]; [CATransaction commit];
I don’t really feel like loading the CGImage from file using CoreGraphics because I’m lazy. But I will if there’s a big performance boost! LoadImage just mangles a string to get the right path for loading said image, and obj is a NSObject-struct that holds all the info I need for this thread.
Help?
There’s not a big performance boost – if anything it’s the other way around. By going throuh UIImage to load up your images, you’ll get all the benefits of caching that it does for you and it’ll be a very speedy critter to use with your various CALayers.