> It would be nice to have this tracing extended to the code that is > being debugged. > It could be an extension/alternative to the stack tracing only the > functions that have been called Could you provide more details about this? Sounds interesting to me.
> In a loop with function-calls, it would be enough (and more > informative) if the number of repeats would be noted instead of naming > the function each time. Yes, I was already thinking about this. I am not sure if just a number would be enough as the text-message can be different each time. The idea was to create a group from logs (which are the same) and come in sequence. So you would see just one log and you could expand it. > This object trace would save a lot of debugging time as it would show > more than the stack-panel There is actually more tabs. Pass an object into the FBTTrace.sysout method (the second parameter) and you should see (depends on the object) at least additional "Properties" tab (in case of network request object there is e.g. additional Response tab). Honza --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
