Hi,
I have the problem in my application. I also have this effect in a test project...
I'll try to reproduce the issue with the steps you provided.
Can you please also provide the version of Delphi you are using?
Yes, thank you.
Hello,
I have been able to reproduce the issue now.
It's possible this is a temporary with the Google Maps API.
after some clicking on the form or the handles or after some minutes comes a message:
I have same problem in FMX version. When resize, application stops.
Once per quarter, the Maps JavaScript API team releases a new version. This happens mid-February, mid-May, mid-August, and mid-November. The next update will be mid-February. The new version will be 3.36. At that time, versions will be updated and the following changes will take place.
So something else is the culprit for all TMS components using Google Maps API not working as expected.
Peter
Choosing the weekly channel
Maybe the weekly channel made some changes!?
For most applications, we recommend the weekly channel. This is the most current and up-to-date version and contains the latest bug fixes and performance improvements. You can specify the weekly channel by loading the Maps JavaScript API with the following script tag:
Currently, the weekly channel is version 3.35. This version is updated weekly with new features, bug fixes, and performance improvements.
Which version of JavaScript are you using?
We've been experiencing the very same issue on our end since yesterday, no change whatsoever on our end. Worked fine the day before and broken as of yesterday.
We also started seeing the reported issue a couple of days ago with no code changes from our side.
We have no control over this as this is most likely an issue with the Google Maps API,
We'll have to investigate if there is a possible workaround available.
After further investigation we have strong indications that this issue is related to a recent Windows update.
Windows updates were installed on a windows 7 computer on 9th of January, but not 15th of January, when the problems started.
As informed, the problem can be reproduced in a standalone Internet Explorer, so it is unrelated to our code in the Windows WebGMaps components.
It appears to be a problem between Internet Explorer and the Google Maps tile server. We thought that the Windows update (which does affect Internet Explorer) was the logical answer to what changed. I'm afraid that only contacting Microsoft and Google can reveal what is really happening here.
I could not reproduce it with Internet Explorer on windows 7 machine.
I also couldn't reproduce it with Internet Explorer
Are you effectively testing the Google Maps JavaScript API? This is different from simply navigating to maps.google.com!