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.
This is freeze is not a crash. The display stays up and tiles might even continue to load around the edges. But all of the touch events are no longer recognized.
I can workaround but hitting the navigation button to zoom to the full extents of the map and then the touch events are again recognized.
It appears that it may be a kind of race condition with tile loading. I've triggered it when zooming out and rotating - I can see tiles around the borders are missing and when they start loading and displaying then the freeze happens.
Seeing this on an iPhone 5c (Model A1456, A1532) with iOS 7.1.1 (11D201) both in debug and release mode.
The text was updated successfully, but these errors were encountered:
Yeah, going to look into this still. Relates to a forced un-rotate at low zooms that we don't want gestures to interrupt. Cases where this happens in MVKMapView.h:
Finally tracked this down to deadlock problems with animated rotation followed by an unchecked notify_map_change() which needs to get lat, lon, and zoom. Fix almost in.
This is freeze is not a crash. The display stays up and tiles might even continue to load around the edges. But all of the touch events are no longer recognized.
I can workaround but hitting the navigation button to zoom to the full extents of the map and then the touch events are again recognized.
It appears that it may be a kind of race condition with tile loading. I've triggered it when zooming out and rotating - I can see tiles around the borders are missing and when they start loading and displaying then the freeze happens.
Seeing this on an
iPhone 5c (Model A1456, A1532)
with iOS7.1.1 (11D201)
both in debug and release mode.The text was updated successfully, but these errors were encountered: