KeyDragZoom 2.0.1 released

[Gary Little]

I have just released KeyDragZoom 2.0.1. In this release, the visual
control remains above the veil pane so that you can turn off drag zoom
(after you click the control but before you start dragging) simply by
clicking the control once again.

With KeyDragZoom you can add the same type of drag zoom capability
that is currently used on maps.google.com to your own maps -- except
that the implementation is more complete (supports tool tip help,
ability to set a cursor (crosshair is the default)). And, of course,
you can also trigger the drag zoom from the keyboard by holding down a
hot key (usually Shift, but can be set to Ctrl or Option/Alt).

[Ela]

Hey, I’m actually using the keydragzoom in one of my projects but have
modified it a little bit to just use the selection rectangle without
zooming into the selected bounds. I use this to selected all markers
within the selection bounds.
The implementation of the selection rect is nice, so maybe you can add
an option to enable/disable the zoom function, or make the zoom to
selection a method of the drag object?!

Another "feature" I would suggest is the ability to Disable/Enable the
feature. There are two methods to disable the keydragzoom completely
but it is not bug free.
I've modified your script for my project to disable the drag object
temporarily. The best way would be to implement a setMap method for
the drag object which is working correctly, because if you do this
now, you'll get a ton of errors... All gmap V3 objects have this
feature to disable the object with setMap(null), maybe you can add
this to this utility, too.
(Disabling this feature doesn't mean removing the divs and event
listeners completely! I needed this because after my user selects
something, the selection feature shouldn't be available until the
selection is cleared, so I'm constantly enabling / disabling this
feature. Using the provided methods to enable disable the keydrag
object (removing/creating it) leads to memory leaks and problems or
didn't work at all because your disable implementation is not very
sophisticated ;) )

yea that’s it, thanks
m