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.
In some contexts, Backend::activate can be called when the backend is already active. One example is if Map::addLayer is called during notifications such as MapChangeWillStartRenderingFrame and MapChangeRegionDidChangeAnimated.
Therefore Backend::activate / Backend::deactivate need to count the number of calls in a reference counting manner. Deactivation should happen only when the count reaches 0.
I feel like we did this at one point. Did it regress as part of the Backend changes?
In some contexts,
Backend::activate
can be called when the backend is already active. One example is ifMap::addLayer
is called during notifications such asMapChangeWillStartRenderingFrame
andMapChangeRegionDidChangeAnimated
.Therefore
Backend::activate
/Backend::deactivate
need to count the number of calls in a reference counting manner. Deactivation should happen only when the count reaches 0.I feel like we did this at one point. Did it regress as part of the
Backend
changes?cc @kkaefer @boundsj
The text was updated successfully, but these errors were encountered: