This actually is the group for developer's Mapplets questions - since the Mapplets API is just a transformation of the JS Maps API, it seems best to have them share the same group.
But anyway, I've set a filter to catch mapplet questions as I know not many folks are necessarily familiar with them. Regarding the question - are you in Firefox 2 or Firefox 3? There are known issues with FF3, console.log, and Firebug. I personally only use Firefox 2 for debugging these days. - pamela On Tue, Sep 9, 2008 at 6:44 PM, olracid <[EMAIL PROTECTED]> wrote: > > I switched from using the Mapplet Scratch Pad to running my own HTTP > server, added my Mapplet that way and all the console.log() messages > show up that way...even when repeatedly reloading it. > > On Sep 9, 2:54 pm, olracid <[EMAIL PROTECTED]> wrote: >> I like the fact that Firebug logs console.log() can be used to trace >> messages. >> >> But what I'm seeing with Firebug v1.2.0b15 on FireFox 3.0.1 is that >> the trace message only works the first time "Preview" the Mapplet in >> the "Mapplet Scratch Pad." >> >> If I take and return to the editor and then preview again, no tracing >> occurs. I have to restart the browser to get tracing to work (and >> that is only the first time I use it). >> >> As a simple test, I loaded the "Hello World" from the bottom of the >> "Mapplet Scratch Pad", put in a single line to of "console.log())" and >> then retried. I get the same results (so I'm inferring it's not my >> code). >> >> Has anyone else experienced this...perhaps I'm missing something >> simple? >> >> Thanks! > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
