The bugs found around 180 (E/W) degree in longitude

[kelpinswamp]

Dear Sir:
Tks to your good web site and app, they help a lot to my job.

Here are the bugs:

1.Near the longitude of 180 degree, the weather picker will disappear automaticly whenever I move the cursor from west to east nor from east to north, crossing the 180 degree line.
2.The "distance and planning" functions abnormally when long crossing 180 degree line ,sometimes indicate halfly(attched pic, distance line 1-2), sometimes the route will go with peculiar turn (attched pic, distance line2-3).
3.My favorite location cannot display simultaneously when they are spreading from E and W. And the favorite location around 180 degree in longitude will never display.

Here are suggestions:

1. Would you pls stop the function of double click with "zoom"? Because too often the sigle left click is interrupted.

2.Would you pls do some improvement for Edge browser? Because the Laltitude figure on the left edge will not show.

3.Would you pls do some enhancement to "distance and planning" function? For example, we can input mannually with the precise location we want, not only by cursor pointing. And also, introducing the function of route planning, hence we can import the points from excel form.

Tks for your watching and kindness help.

[kelpinswamp]

@kelpinswamp
sorry just pic too big, now adusted ok.

[kelpinswamp]

{
"runningMs": 5838610,
"type": "user",
"module": "Evented",
"msg": "Failed to call toggle: 'riot' is not defined",
"url": "https://www.windy.com/?2018-08-12-06,14.009,-158.522,6,i:pressure,m:dVOat6",
"ver": "15.15.0",
"target": "index",
"stack": "ReferenceError: 'riot' is not defined
at _open (https://www.windy.com/v15.15.0/index.js:48:511)
at open (https://www.windy.com/v15.15.0/index.js:48:343)
at f (https://www.windy.com/v15.15.0/index.js:50:311)
at h (https://www.windy.com/v15.15.0/index.js:50:623)
at emit (https://www.windy.com/v15.15.0/index.js:11:412)
at defaultClickHandlers (https://www.windy.com/v15.15.0/index.js:56:583)
at onevent (https://www.windy.com/v15.15.0/index.js:56:410)",
"latestBcast": "render: rendered tileLayer (4882ms. ago)
render: rendered particles (4882ms. ago)
bcast: redrawFinished (4674ms. ago)
bcast: toggle lhpane (3546ms. ago)
bcast: toggle lhpane (1ms. ago)
",
"sessionName": "ap-gangu-county-3500-10500-50",
"sessionCounter": 10,
"lang": "zh",
"retina": true,
"size": "1745x982",
"glParticles": true,
"platform": "desktop",
"errorID": "failed-to-call-toggle-riot-is-not-defined"
}
Error no: 2
{
"runningMs": 5848983,
"type": "user",
"module": "Evented",
"msg": "Failed to call toggle: Unable to get property 'addEventListener' of undefined or null reference",
"url": "https://www.windy.com/?2018-08-12-06,14.009,-158.522,6,i:pressure,m:dVOat6",
"ver": "15.15.0",
"target": "index",
"stack": "TypeError: Unable to get property 'addEventListener' of undefined or null reference
at addHooks (https://www.windy.com/v15.15.0/index.js:66:639)
at _open (https://www.windy.com/v15.15.0/index.js:48:511)
at open (https://www.windy.com/v15.15.0/index.js:48:343)
at f (https://www.windy.com/v15.15.0/index.js:50:311)
at h (https://www.windy.com/v15.15.0/index.js:50:623)
at emit (https://www.windy.com/v15.15.0/index.js:11:412)
at defaultClickHandlers (https://www.windy.com/v15.15.0/index.js:56:583)
at onevent (https://www.windy.com/v15.15.0/index.js:56:410)",
"latestBcast": "render: rendered particles (15255ms. ago)
bcast: redrawFinished (15047ms. ago)
bcast: toggle lhpane (13919ms. ago)
bcast: toggle lhpane (10374ms. ago)
bcast: toggle lhpane (2ms. ago)
",
"sessionName": "ap-gangu-county-3500-10500-50",
"sessionCounter": 10,
"lang": "zh",
"retina": true,
"size": "1745x982",
"glParticles": true,
"platform": "desktop",
"errorID": "failed-to-call-toggle-unable-to-get-property-addeventliste"
}

[Marienka]

Hi @kelpinswamp , many thanks for your reports and screenshot! First of all, we're really happy that Windy is of a good help to you! :)

Regarding the 180° picker issue, we know about this problem and unfortunately it cannot be fixed (please check this link).

As to your other reports and suggestions, we will have a look at it and see what can be done.