I tried debugging the code right before I do the check on the _data.code and it blows up before that so checking on NO_NEARBY_PANO doesn't seem to be the answer. The check on the _data.code happens after the call to Google but it seems that it's blowing up in the Google code and not when it gets back. Hence the error that is occurring which is Google's code:
'undefined' is null or not an object main.js, line 1325 character 74 Maybe I'm missing something or misunderstood your response? --Chris On Mar 4, 6:34 pm, Andrew Leach <[email protected]> wrote: > On Mar 4, 10:22 pm, Chris <[email protected]> wrote: > > > > > Any ideas on what is wrong with this LatLon and how I can at least > > catch this error because the try/catch isn't catching it. > > In your example, _data.code is 600, NO_NEARBY_PANO. That seems fairly > explicit: there's nothing to show near that location. You should be > testing for this code (as you are in your example), not using a try/ > catch. In your example, try/catch won't work because the callback > function is called asynchronously, outside the main flow of execution. > The main flow never errors. -- 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.
