Draws the contents of the overlay view.
- iOS 4.0–7.0Deprecated
- Mac Catalyst 13.0–13.0Deprecated
The map rectangle that needs to be updated. You can use this rectangle to limit drawing to only the portion of the view that changed.
The current scale factor applied to the map content. You can use this value for configuring the stroke width of lines or other attributes that might be affected by the scale of the view’s content.
The graphics context to use for drawing the view’s content.
The default implementation of this method does nothing. Subclasses are expected to override this method (instead of the
draw method) and use it to draw the contents of the view.
In your drawing code, you should specify the position of any rendered content relative to the map itself and not relative to the view’s bounds or frame. In other words, compute the position and size of any overlay content using map points and map rectangles, convert those values to
CGRect types (using the methods of this class), and then use the converted points to build paths or specify the rendering location for items.
You should also not make assumptions that the view’s frame matches the bounding rectangle of the overlay. The view’s frame is actually bigger than the bounding rectangle to allow you to draw lines for things like roads that might be located directly on the border of that rectangle. For some types of content, such as gradients, this also means that you might need to apply a clipping rectangle to
context to ensure drawing is contained to the correct area.
It is recommended that you use Core Graphics to draw any content for your overlays. If you choose to use UIKit classes and methods for drawing instead, you must push the specified graphics context onto the context stack (using the
UIGraphics function) before making any drawing calls. When you are done drawing, you must similarly pop the graphics context off the stack using the
UIGraphics. During drawing, you may draw content normally but should avoid manipulating views and other classes that are safe to use only from the application’s main thread.
To improve drawing performance, the map view may tile overlays that become large enough and render the tiles from separate threads. Your implementation of this method must therefore be capable of safely running from multiple threads simultaneously. In addition, you should avoid drawing the entire contents of the overlay each time this method is called. Instead, your implementation should always take the
map parameter into consideration and avoid drawing content outside that rectangle. Failure to do so could lead to performance problems.