I looked at the source change and the hack is similar to what I tried with temporarily removing handlers, so I imagine it is fixed. But I haven’t had much luck compiling the extensions myself so I’m not sure if its fixed. I pulled from the master branch and compiled GoogleMaps, copied the DLL and XML to the ProgramFiles\IceTeaGroup\bin, and rebuilt my solution, but the MapClick event still fires when closing a messagebox on mobile. So it may be fixed but maybe I just haven’t updated my extension correctly. Is it possible to try this in an interim build?
thanks
Andrew
The source had the hack, and the newer DLL is in my project bin directory, so I’m starting to think it did not work. Still getting the MapClick event firing from the messagebox.
Just to make sure your server is running the updated extension, do the changes show up in JavaScript sources on your browser? Doesn’t have to be a mobile browser…
As far as I can tell: https://snag.gy/XRUO1J.jpg … not sure why it is showing up there, and only that .js file. Breakpoints set on it show up in the wrong spot and don’t seem to do anything.
Unfortunately the hack doesn’t work since it’s based on the timestamp difference between events. I don’t have a solution to this google maps bug/feature at the moment. You can use map.setClickable(true | false) to disable clicks on the map.
that setClickable function is only for a marker. to workaround we’d need to disable clicks for the entire map. if the new potential fix does not work can you provide code to call map.setClickable? (if it exists)
