You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let say i want to click on the globe and the browser most alert me back the latitude of the place that i have clicked. What i did was this:
earth.on('click', fire);
var fire = function(e) {
alert('You clicked at ' +e.latitude);
};
it worked on the web browser and retuned the latitude, but it did not work on the mobile( iPhone ) browser.
so what i did next was this instead:
earth.on('touchstart', fire);
var fire = function(e) {
alert('You clicked at ' +e.latitude);
};
it works on the mobile browser (iPhone), but the problem it dont return latitude. Instead it alert me with "NULL". I want it to return the latitude when i touch the globe in the mobile browser.
Please fix it
The text was updated successfully, but these errors were encountered:
sarahansen223h
changed the title
Phone Browser dont return latitude
Touch event dont alert latitude
Jun 15, 2015
This is an open-source project - feel free to fix the source code and provide a patch.
Or do you prefer to support the development time we need to fix it and release update?
Estimate @klokantech is 2 hours: purchased at http://www.maptiler.com/support/one-to-one/
FYI - a 'touchend' event does not receive the latlng property populated. As a work-around just save the event.latlng property in a 'touchstart' event and reuse in the 'touchend' event.
earth.on('click', fire);
var fire = function(e) {
alert('You clicked at ' +e.latitude);
};
it worked on the web browser and retuned the latitude, but it did not work on the mobile( iPhone ) browser.
so what i did next was this instead:
earth.on('touchstart', fire);
var fire = function(e) {
it works on the mobile browser (iPhone), but the problem it dont return latitude. Instead it alert me with "NULL". I want it to return the latitude when i touch the globe in the mobile browser.
Please fix it
The text was updated successfully, but these errors were encountered: