On Nov 25, 5:43 pm, Manoj <[EMAIL PROTECTED]> wrote:
>
> How are you using the onCall() callback currently?
> Will it be safe to chain it to other listener(s)?
...
Well this is supposed to support monitoring calls, but I've never seen
it in action.
>From what I can tell, the result should be these calls for monitored
methods:
frame = getStackFrame(frame, context);
Firebug.Console.log(frame, context);
which is close to what you need for raw input.
Seems like we should move that code to Firebug.console, make it a
debug listener, and dispatch "onCall" with [context, frame].
>
> > Firebug console? Firebug tracing console? OS console? Both of which?
>
> The firebug tracing console. for e.g. all the messages from
> FBTrace.sysout() etc. that appear as "FTS0: ..."
> I figured it out, initially my command line was:
>
> "C:\Program Files\Mozilla Firefox\firefox.exe" -console -no-remote -P
> dev > log.txt
>
> which results in log.txt being created but nothing goes there.
>
> After removing the "-console" option the redirection to the log file
> works. Any FF option to specify both console and output file?
None that I know of, but FTS0 means you did not succeed in opening the
Firebug tracing console. You probably want Firebug Menu > Options >
Always Open Firebug Tracing.
>
> Thanks,
> Manoj
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Firebug" 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/firebug?hl=en
-~----------~----~----~----~------~----~------~--~---
