Closed GoogleCodeExporter closed 8 years ago
Both maps are covered in gray when you press the hot key because they both
receive the keydown event and
react by highlighting themselves. At this point it is impossible to know which
map is going to be clicked, so this
is the correct behavior. Once the mouse drag starts on one map, I suppose it
would be nice if the other map
returned to normal, but that would mean adding considerable more complexity --
would need a class method
that could be called from one map to turn off highlighting of the other map;
the class would have to keep track
of all active instances for this to work. This would get even trickier if the
hot key was different for the other map
-- you'd have to check for that and do nothing if that was the case. Perhaps
Nianwei has some ideas on
implementing this (or whether it's really worthwhile).
Original comment by garylitt...@gmail.com
on 8 Mar 2009 at 9:58
Hmm..what if you only did the grey cover on the map that the mouse cursor was
currently over?
Original comment by pamela.fox
on 8 Mar 2009 at 11:09
There probably no perfect solution for this cause the user expectation may vary
on
different situation. I put in an extra condition of "activation" that shows
behavior
Pamela described. Basically, only the one with mouse on get activated. There are
still minor potential usability issue, but I think the chance of running into
them is
so slim that it's probably not worth the risk to break other behavior.
See r958 for the new version.
http://gmaps-utility-library-dev.googlecode.com/svn-history/r958/trunk/keydragzo
om/examples/multimap.html
Original comment by nian...@gmail.com
on 9 Mar 2009 at 3:24
merged Gary's code in r963
Original comment by nian...@gmail.com
on 16 Mar 2009 at 2:04
Original comment by pamela.fox
on 23 Jun 2009 at 9:24
Original issue reported on code.google.com by
pamela.fox
on 8 Mar 2009 at 8:28