Or I just ask a tongue in cheek question and not post a link to a project that I am working on. My point was that the messages coming back are pretty poor, is there, perhaps, a better way to debug?
On Aug 20, 10:58 am, "Nick B" <newsprof...@gmail.com> wrote:
> Or I just ask a tongue in cheek question and not post a link to a project
> that I am working on. My point was that the messages coming back are pretty
> poor, is there, perhaps, a better way to debug?
Many of us can spot the problem, even with the poor messages, but only
if we can see the code and run it on our debuggers.
I'll suggest, (again), that you follow the group's posting guidelines
if you want free help, and post alink to your map. (not code!)
I understand the "guidelines" as have been on here for ages. However, I'm not asking for you to go through my code, I'm asking how you'd go about debugging this error which gives pretty much zip about what it is.
For example, when you say "run it on our debuggers", are you meaning firebug? Any other tools I can use?
The guidelines say that I souldn't post code, which I haven't. If I was asking for help with the actual script I would post a link, but I'm not. I don't want to display my work until it's finished.
On Wed, Aug 20, 2008 at 10:05 AM, marcelo <marcelo...@hotmail.com> wrote:
> On Aug 20, 10:58 am, "Nick B" <newsprof...@gmail.com> wrote: > > Or I just ask a tongue in cheek question and not post a link to a project > > that I am working on. My point was that the messages coming back are > pretty > > poor, is there, perhaps, a better way to debug?
> Many of us can spot the problem, even with the poor messages, but only > if we can see the code and run it on our debuggers. > I'll suggest, (again), that you follow the group's posting guidelines > if you want free help, and post alink to your map. (not code!)
On Aug 20, 11:41 am, "Nick B" <newsprof...@gmail.com> wrote:
> I understand the "guidelines" as have been on here for ages. However, I'm
> not asking for you to go through my code, I'm asking how you'd go about
> debugging this error which gives pretty much zip about what it is.
There is no standard method. It's just that some of us can,
(sometimes), spot the problem when we see it in action.
main.js is an API file, and as you probably know, it is obfuscated,
but some of us have seen enough errors that we can tell what's going
on anyway. (again, sometimes).
> I
> don't want to display my work until it's finished.
I step back up the run time stack from the point of error to see what
is causing
the error at a higher level in the code ie it often gets you back in
the user code.
Learning to debug efficiently takes practice and experience in situations where the initial error message isn't very meaningful.
The sort of things that I try are looking back up the call stack to find the line of non-API code that provoked the API to produce that error, and display the values of the variables that it passed to the API.
It's taken just a couple of minutes to discover where it is ... (GStreetviewPanorama), however the question was r.e. the low info on error from the external js. Am I missing something on getting back better information?
Not being an experienced javascript programmer, I just discovered the debugger command. And firebug allows me to step through line by line. It'd be nice to share some hints and tips on this area?
Nick
On Wed, Aug 20, 2008 at 4:51 PM, Mike Williams <nos...@econym.demon.co.uk>wrote:
> Wasn't it Nick B who wrote: > >is there, perhaps, a better way to debug?
> Learning to debug efficiently takes practice and experience in > situations where the initial error message isn't very meaningful.
> The sort of things that I try are looking back up the call stack to find > the line of non-API code that provoked the API to produce that error, > and display the values of the variables that it passed to the API.
