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.
The MapChange enumeration values have their roots in MapKit semantics -- yet are increasingly deviating from those semantics, or expanding on them. We should replace them with an API that is less influenced by the API of a particular platform, and more influenced by the pattern we use elsewhere for observation, e.g. the style observer. It should be general enough that MapKit-like change notifications can be built on top of it.
The text was updated successfully, but these errors were encountered:
The MapChange enum was never particularly well-suited for MapKit semantics, either, because it was impossible to provide relevant context, such as a camera or error pointer, with a change notification. Awhile back, I started experimenting with making map change notifications more object oriented in the 1ec5-delegate-fail-loading-6142 branch, but imitating the style observer would be even better.
jfirebaugh
changed the title
Replace MapChange enum and View::notifyMapChange with dedicated observer interface
Replace MapChange enum and Backend::notifyMapChange with dedicated observer interface
Dec 16, 2016
The
MapChange
enumeration values have their roots in MapKit semantics -- yet are increasingly deviating from those semantics, or expanding on them. We should replace them with an API that is less influenced by the API of a particular platform, and more influenced by the pattern we use elsewhere for observation, e.g. the style observer. It should be general enough that MapKit-like change notifications can be built on top of it.The text was updated successfully, but these errors were encountered: