Re: [mapguide-users] Google strikes again (v3.1.2)

2019-12-12 Thread Kajar
Good to know. Then I use also weekly option. By the Google api doc I should setup it like below, but this is not working for me: js?v=weekly=YOUR_API_KEY"> Using ...v=weekly seems to work. Is it correct way to define key for mapguide map? -- Sent from:

Re: [mapguide-users] Google strikes again (v3.1.2)

2019-12-12 Thread RenoSun
The Town of Qualicum Beach's GIS is still using MG 3.1.2 and Google Maps API Weekly Version. It seems having no shift issues displaying its map with Google Maps API using WGS 84 / Pseudo-Mercator coordinate system.

Re: [mapguide-users] Google strikes again (v3.1.2)

2019-12-12 Thread Kajar
Can someone please tell me also how to define correctly version parameters for API key. Currently I was using: .v=3.35use_slippy=true Now when I use same way(use 3.37 instead 3.35) I will get warning: You have included the Google Maps JavaScript API multiple times on this page. This may cause

Re: [mapguide-users] Mapguide 4K issue

2019-12-12 Thread Kajar
Thanks! I tried to reduce window size and WMS layers become visible, this is indeed related to wms layer default values like you have described. -- Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html ___ mapguide-users

Re: [mapguide-users] Google strikes again (v3.1.2)

2019-12-12 Thread Kajar
Now I'm getting another error, maybe this is causing issues and not Google: Error: fusionSF.js:50778 [Intervention] Unable to preventDefault inside passive event listener due to target being treated as passive. See https://www.chromestatus.com/features/6662647093133312 preventDefault @