title: Does MKOverlayPathView need drawMapRect?
body: <p>I'm having some inconsistencies modifying the Breadcrumb example, to have the CrumbPathView subclassed from MKOverlayPathView (like it's supposed to) rather than subclassed from MKOverlayView. </p>
  
  <p>Trouble is, the docs are limited in stating the difference in how these 2 should be implemented. For a subclass of MKOverlayPathView it's advised to use:</p>
  
  <pre><code>- createPath
  - applyStrokePropertiesToContext:atZoomScale:
  - strokePath:inContext:
  </code></pre>
  
  <p>But is this in place of drawMapRect, or in addition to? It doesn't seem like much point if it's in addition to, because both would be used for similar implementations. But using it instead of drawMapRect, leaves the line choppy and broken.</p>
  
  <p>Struggling to find any real world examples of subclassing MKOverlayPathView too...is there any point?</p>
  
  <p>UPDATE - modified code from drawMapRect, to what should work:</p>
  
  <pre><code>- (void)createPath
  {
      CrumbPath *crumbs = (CrumbPath *)(self.overlay);
  
      CGMutablePathRef newPath = [self createPathForPoints:crumbs.points
                                      pointCount:crumbs.pointCount];
  
      if (newPath != nil) {
          CGPathAddPath(newPath, NULL, self.path);        
          [self setPath:newPath];
      }
  
      CGPathRelease(newPath);
  }
  
  
  - (void)applyStrokePropertiesToContext:(CGContextRef)context atZoomScale:(MKZoomScale)zoomScale
  {
      CGContextSetStrokeColorWithColor(context, [[UIColor greenColor] CGColor]);
  
      CGFloat lineWidth = MKRoadWidthAtZoomScale(zoomScale);
      CGContextSetLineWidth(context, lineWidth);
  
      CGContextSetLineJoin(context, kCGLineJoinRound);
      CGContextSetLineCap(context, kCGLineCapRound);
  }
  
  
  - (void)strokePath:(CGPathRef)path inContext:(CGContextRef)context
  {
      CGContextAddPath(context, path);
      CGContextStrokePath(context);
  
      [self setPath:path];
  }
  </code></pre>
  
  <p>This draws an initial line, but fails to continue the line...it doesn't add the path. I've confirmed that applyStrokePropertiesToContext and strokePath are getting called, upon every new location.</p>
  
  <p>Here's a screenshot of the broken line that results (it draws for createPath, but not after that):</p>
  
  <p><img src="https://i.stack.imgur.com/2UpeB.jpg" alt="Breadcrumb example with createPath instead of drawMapRect"></p>
  
  <p>Here's a screenshot of the "choppy" path that happens when drawMapRect is included with createPath:</p>
  
  <p><img src="https://i.stack.imgur.com/QLMsF.jpg" alt="Broken map path"></p>