You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
MGLAnnotationImage uses a delegate pattern to update MGLMapView, so an MGLAnnotationImage instance can only be used with a single MGLMapView instance. Yet there’s nothing in the API that would communicate this limitation to the developer. Instead of delegation, MGLMapView should observe changes to each MGLAnnotationImage’s image. Whether we use KVO or NSNotificationCenter, MGLMapView would probably have to track or compute on the fly whether any annotations are currently using an MGLAnnotationImage that is getting modified.
MGLAnnotationImage uses a delegate pattern to update MGLMapView, so an MGLAnnotationImage instance can only be used with a single MGLMapView instance. Yet there’s nothing in the API that would communicate this limitation to the developer. Instead of delegation, MGLMapView should observe changes to each MGLAnnotationImage’s image. Whether we use KVO or NSNotificationCenter, MGLMapView would probably have to track or compute on the fly whether any annotations are currently using an MGLAnnotationImage that is getting modified.
/cc @boundsj
The text was updated successfully, but these errors were encountered: