MKMapView: need dragging/zooming properties
| Originator: | futuretap | ||
| Number: | rdar://13216416 | Date Originated: | |
| Status: | Closed/Behaves correctly | Resolved: | |
| Product: | iPhone SDK | Product Version: | 6.0 |
| Classification: | Feature (New) | Reproducible: | Not Applicable |
Similar to UIScrollView, I'd like to propose the following readonly properties to MKMapView: @property(nonatomic, readonly, getter=isDragging) BOOL dragging @property(nonatomic, readonly, getter=isZooming) BOOL zooming This would be handy in various circumstances for programmatic region handling. For instance to block new region changes until the map stands still. Another use case would be to implement a custom tap gesture recognizer that doesn't interfere with tap-to-stop-panning. 30-Apr-2013 11:19 PM Apple Developer Bug Reporting Team : Engineering has determined that this issue behaves as intended based on the following information: You can already achieve this by using the region change delegate callbacks: - (void)mapView:(MKMapView *)mapView regionWillChangeAnimated:(BOOL)animated; - (void)mapView:(MKMapView *)mapView regionDidChangeAnimated:(BOOL)animated; Set a flag in the app between those callbacks and avoid setting a region or allowing gestures when the flag is set. 02-May-2013 11:23 AM Ortwin Gentz: That's what we're currently doing. We can't differentiate scrolling and zooming, though. And I believe I saw cases where the number of regionWillChange calls was not identical to the number of regionDidChange calls. I'll be at the WWDC MapKit lab and will be happy to discuss in detail.
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!