Is drawRect: called on multiple threads when using a CATiledlayer?
It doesn't answer your question directly, but it could help you decide how to implement your model.
That article contains a contradiction, but it pretty much says you have to be threaded. Watching the WWDC session video gives me one more piece of the puzzle that convinces me that this is the case. – Steve Weller Jun 19 '10 at 3:22.
Yes, drawRect can and will be called on multiple threads (tested on OS 4.2). This behaviour is less obvious if your drawing is fast enough to outpace the arrival of new zoom gestures so your app may work fine until tested with rapid input of zoom gestures. One alternative is to make your model thread-safe.
If thread-safety is achieved by synchronizing most of the access to the data model to one drawing thread at a time then then you might do just as well to mutex the boy of drawRect with something like @syncrhonize(self) which seems to work. I haven't found a way to request that CATiledLayer only uses one background thread.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.
Related Questions
CATiledLayer or CALayer drawing UIImage not working?
IPhone: why isn't drawRect getting called?
IOS: Why is drawRect: being called twice, and why does this ivar value seemingly change without any reason?
Core Graphics- drawRect: not getting called frequently enough?
Simple UIView drawRect not being called?
UIView subclass in XIB doesn't display (drawRect: never called)?