05.11.2010, 11:36
(03.11.2010, 19:01)routeconverter Wrote: But this shouldn't be a problem anymore when the triple insert is fixed.
This is weird... RouteConverter gets a lot of insert-position requests from the web browser:
Quote:Nov 3, 2010 9:40:33 PM slash.navigation.converter.gui.mapview.BaseMapView processCallbacks
INFO: processing callback GET /insert-position/48.76886223397753/2.41424560546875 HTTP/1.1
Nov 3, 2010 9:40:33 PM slash.navigation.converter.gui.mapview.BaseMapView processCallback
INFO: inserting position GET /insert-position/48.76886223397753/2.41424560546875 HTTP/1.1
Nov 3, 2010 9:40:33 PM slash.navigation.converter.gui.mapview.BaseMapView processCallbacks
INFO: processing callback GET /insert-position/48.76886223397753/2.41424560546875 HTTP/1.1
Nov 3, 2010 9:40:33 PM slash.navigation.converter.gui.mapview.BaseMapView processCallback
INFO: inserting position GET /insert-position/48.76886223397753/2.41424560546875 HTTP/1.1
Nov 3, 2010 9:40:33 PM slash.navigation.converter.gui.mapview.BaseMapView processCallbacks
INFO: processing callback GET /insert-position/48.76886223397753/2.41424560546875 HTTP/1.1
It seems this JavaScript from contextmenucontrol.js produces them:
GEvent.addDomListener(entry, "click", function () {
if (arg == "insert") {
me.insertPosition_();
ContextMenuControl.prototype.insertPosition_ = function () {
var me = this;
var point = me.clickedPoint_;
callJava("insert-position/" + point.lat() + "/" + point.lng());
};
I don't see a bug there... you? Are you able to debug this?
--
Christian
Christian
