Angular-google-maps: No smooth dragging

[andresguibarra]

Issue description

Hello, I started to notice that I can no longer smooth drag the map. It starts to lag as soon as I try to drag it.

Expected/desired behavior
Smooth dragging.

angular2 & angular-google-maps version
1.0.0-beta.2

[mrubka]

Hello, I am having exactly the same issue, When dragging, map moves a few pixels and then suddenly stops, you have to release mouse button, but it happens every time when trying to drag map.

[gabrieltaets]

same issue here, using angular 5

[ziftytodd]

Same here, and without any change to our code that was working fine until yesterday. I'm thinking it must be something that Google changed that broke something in this project.

[ziftytodd]

Google released a new version of their JS API, which uses a new renderer that apparently has caused the problem. A short-term workaround is to use the old version. The old version will only work until August, at which point this project will need to be fixed. To force the old version until August, just add apiVersion: '3.31' in your app.module.ts where you initialize the AgmCoreModule. Like this:

AgmCoreModule.forRoot({
  apiKey: '[YOUR_KEY_HERE]',
  apiVersion: '3.31'
})

This will bring back dragging (until August, at which point Google will not honor the request for 3.31 version any longer)

[gabrieltaets]

Thanks @ziftytodd, that worked like a charm. I was going crazy trying to figure out whether it was my app, the library or Google API's fault.

[lluisnieto]

Jesus Christ, I was going mad. I can't believe Google have this crap on production. Downgrading the version solved everything.

[ziftytodd]

@gabrieltaets I wouldn't advise marking this as "solved", as it will break again in August once Google no longer honors requests for older versions of their API.

Ultimately, a fix is needed to this library, as using the Google Maps API without this library works fine for dragging. Something in the library isn't playing nice with the updated Google Maps API.

[gabrieltaets]

@ziftytodd I agree. The OP however is @andresguibarra, not me. Anyway, I might look into the library in the next weeks to try and figure out what's happening and make a PR in case I can fix this

[miiihi]

The problem is in two way binding to lat/lng and centerChanged event. We need to differentiate between center change coming from map internal events (drag) and from changes that we're introducing thru lat/long inputs. For that, we need a private map lat/lng. Otherwise two way binding cancels out center changes from drag events...

Fix available in #1413

[Zerendipity]

This is starting to become critical right? When in august will this project break?
Will there be a new version coming out soon?

[csmcgee]

Noticed smooth dragging is gone even with api-version adjustment mentioned in earlier post. I would say this is a critical issue now.

[Fender123]

this is issue is also critical for my project. @SebastianM are you going to merge #1413 and release a new version soon?

[lluisnieto]

Need to fix this asap, very bad user experience. I tried to implmenent "miiihi's" solution but did not work: zoom in, out is still awful.

[friedolinfoerder]

When will it be merged?

[gabrieltaets]

bump?

[miiihi]

Solution is one click (merge) away in #1413
The requested changes from Jun 2nd have been addressed on Jun 4th, since then the PR is ready to merge - I've even rebased it couple of days ago...
But it looks like @SebastianM has abandoned this lib?

[jezewski]

Bumping, it's been another week with this going nowhere. @SebastianM Would it be possible to bring on some help with this project?

[Fender123]

@miiihi there seems to be a problem with zooming multiple zoom levels at once (only possible on touch devices). After you have reached the next zoom level your pinch to zoom gesture doesn't work anymore. Seems related to the bug you've fixed. Do you have an idea how to fix this?

[jimmykane]

Looks like this lib is getting worse and worse, although it has beeen widely used.

Suggestion: @SebastianM if you are not going to get busy with this please mark the project something as deprecated or so. Currently as time passes more and more components are not working well.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.