Closed GoogleCodeExporter closed 9 years ago
internal ref 1829355
Note that I have been unable to reproduce this outside the maps demo, with
neither
straight JavaScript or a small GWT demo.
Original comment by galgwt.reviews@gmail.com
on 5 May 2009 at 6:03
I've reproduced this issue:
- Create any map during module load and put it on the page.
- Some time after the onModuleLoad() completes and the first map displays,
create a
second map
- Include a click handler,
- Use MapWidget.setUItoDefaults().
- Display the second map on the page.
Although this is not typical for a Maps application, it just so happens that
our Maps
demo performs all of the following.
Known workarounds. Any single one of the measures below seems to prevent the
bug.
- Use a single MapWidget
- If you use multiple map widgets, create them in onModuleLoad(), don't defer
creating them.
- Don't call MapWidget.setUItoDefaults() when you want to use a MapClickHandler
- Turn off the DoubleClickToZoom feature from the MapUIOptions:
MapUIOptions opts = map.getDefaultUI();
opts.setDoubleClick(false);
map.setUI(opts);
Original comment by galgwt.reviews@gmail.com
on 6 May 2009 at 2:36
Attachments:
Original comment by zundel@google.com
on 21 Dec 2009 at 1:32
A patch was applied to the GWT demo to set the UI options, turning off double
click as
shown in the workarounds above.
Original comment by zundel@google.com
on 8 Apr 2010 at 6:45
Original issue reported on code.google.com by
galgwt.reviews@gmail.com
on 5 May 2009 at 6:00