I tried to take a look at the first example. (The second one gave a 500 error.) In particular I wanted to see what functions and blocks were nested inside of what. But the indentation is all over the place and I couldn't make sense of it.
So a good place to start would be to fix the indentation. Pick either tabs or a fixed number of spaces (2 or 4 are typical) and make sure everything is indented consistently. Does your editor have a setting to make whitespace visible so you can see whether the code has tabs or spaces, along with a way to easily convert from one to the other? If not, get Komodo Edit [1] (free) and check out the View/View Whitespace and Code/Tabify|Untabify Region menu items. (To use the latter, first set the Editor/Indentation values in Edit/Preferences or Edit/Current File Settings and then select the lines of text you want to convert.) > I thought it might have something to do with waiting a bit > longer for the reversegeocoder to return the values, but that > is not the case. I tried setTimeout. It still shows the last result. Naw, throwing setTimeout() calls at a problem like this blindly is probably not a very reliable way to fix it. How long do you wait? Sometimes a strategic setTimeout() is just the right solution, but my guess is that isn't the case here. Anyway, fix the indentation so it's easier to follow the code, and then somebody may be able to help point you to the problem. Or, as geocodezip mentioned, check Mike Williams' tutorials. -Mike [1]: http://www.activestate.com/Products/komodo_edit/ > I am working on a map, that reverse geocodes a marker's dragged point. > The values of city and state that I am getting on marker > dragging is from the last drag. I think it is just a small > thing that I am missing somewhere which is causing this. I > have tried it on both FF and IE. > > Here is the page that shows issue: http://tinyurl.com/4olejf > > Interestingly, if I add an alert right before adding the city > and state into the infoWindow, the alert shows the wrong > (last) value, but the infoWindow shows the correct value. I > thought it might have something to do with waiting a bit > longer for the reversegeocoder to return the values, but that > is not the case. I tried setTimeout. It still shows the last result. > Here is the URL for the page with the alert: http://tinyurl.com/4rypdr > > Thanks for looking at it. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
