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.
Collision debug toggling should trigger a repaint once the symbol buckets have been updated. This doesn't seem to be the case as the collision boxes are only visible e.g. when enabling collision debug after a second call to MapContext::update().
Current behavior feels correct because usually we are causing more repaints due to e.g. mouse gestures. In GLFW example, if we keep pressing C key the behavior also feels correct because each time we press the shortcut, the previous repaint gives the wrong impression that collision debug state is the same as visible on-screen.
/cc @mapbox/gl
The text was updated successfully, but these errors were encountered:
Collision debug toggling should trigger a repaint once the symbol buckets have been updated. This doesn't seem to be the case as the collision boxes are only visible e.g. when enabling collision debug after a second call to
MapContext::update()
.Current behavior feels correct because usually we are causing more repaints due to e.g. mouse gestures. In GLFW example, if we keep pressing
C
key the behavior also feels correct because each time we press the shortcut, the previous repaint gives the wrong impression that collision debug state is the same as visible on-screen./cc @mapbox/gl
The text was updated successfully, but these errors were encountered: