Hamilton, I've not used geocoding in a gadget for some months, but AFAIK it still works - certainly there's been no published change from Google that would have broken it generally. They do turn various regions on and off as licensing terms shift, but that's a legal change, not a technical one.
One thing that does confuse me is your use of getLatLngAsync. Are you building a mapplet or an ordinary gadget? If the latter, you want to be using getLatLng; the Async version is only in the Mapplets API. In any case, it's hard for us to give specific advice to a general question like yours. Can you supply a link to your gadget XML? String On Dec 2, 5:31 pm, fireball <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to use > > getLatLngAsync > > I'm aware that geocoding wont work without a maps API key for > gmodules.com so, I setup the gadget using the map setup with the > gmodules key string I saw in another message on this group: > > <script src="http://maps.google.com/maps? > file=api&v=2.x&key=ABQIAAAAN_IKAOv-fz9s2G9ZOihkhRTZqGWfQErE9pT- > IucjscazSdFnjBQDYx3NPTITB-lcDbaP-f0SHuFszw&sensor=false" > type="text/javascript"></script> > > and I still can't get geocoding to work. > > Any ideas? The last message I saw on this was in 2007. Have there > been any changes? > > Thanks, > Hamilton --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "iGoogle Developer Forum" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Gadgets-API?hl=en -~----------~----~----~----~------~----~------~--~---
