Specifically designed to work with debugging -- inline, log to file, just to debug output. Integrated with classic and the new windowed debug view.. hell it's even integrated with Dreamweaver. CFTRACE was designed for exactly the purpose you guys are discussing -- it doesn't even run unless debug mode is on.
Well worth the effort to read up on this feature of CFMX.
-- geoff http://www.daemon.com.au/
Scott Barnes wrote:
Oh yeah theres probably a million and one ways to do it etc, just it'd be cool to show it with debug mode and its automatic
Scott P.S How as ya holiday :D
"Geoff Bowers" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
What about CFTRACE?? I do this sort of thing all the time with CFTRACE -- the results log to the debugging stack automatically.
-- geoff http://www.daemon.com.au/
Phil McCluskey wrote:
A CallStack feature (ie in debuging, see what times methods where called etc);
This is easy enough to implement yourself, with a message stack object
which
you instantiate inside other objects. When you call functions on your objects you just add a call to update the message stack:
foo.bar(); foo.messaging.addMessage("called bar()");
A bit of extra coding, but being able to inspect a transaction list for
each
object during debugging makes up for it.
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MX Downunder AsiaPac DevCon - http://mxdu.com/
