So what happens is this:
As you pan around the scene, the animation is being "dampened", meaning that if you stop the mouse it will take a couple more frames for the map to catch up with the mouse. This miniscule delay (something like 10 frames, or 1/6 of a single second makes the panning animation much smoother.
The problem is, a typical user lets go of the mousebutton immediately after dragging. The library will immediately stop movement, but really it should finish the pan-dampening animation in the meantime. What's worse is that then if you proceed to zoom it'll finish panning, which is disorienting.
So what happens is this:
As you pan around the scene, the animation is being "dampened", meaning that if you stop the mouse it will take a couple more frames for the map to catch up with the mouse. This miniscule delay (something like 10 frames, or 1/6 of a single second makes the panning animation much smoother.
The problem is, a typical user lets go of the mousebutton immediately after dragging. The library will immediately stop movement, but really it should finish the pan-dampening animation in the meantime. What's worse is that then if you proceed to zoom it'll finish panning, which is disorienting.