I'll push this little function a little bit further - and display my
favourite debugging function:
<cffunction name="trace">
<cfargument name="variable">
<cfset var output = "">
<cfsavecontent variable="output">
<cfdump var="#arguments.variable#">
</cfsavecontent>
<cftrace text="#output#">
</cffunction>
Which means you can call trace(variables) or whatever anywhere in your
CFC, and see the output in the trace dialog at the bottom of the
screen - well away from the rest of everything else.
HTH
Mark
On 7/21/05, Gary Menzel <[EMAIL PROTECTED]> wrote:
> I'll answer that one - even though it is not my script.....
>
> Because then you can catch the output in a variable (returned from the
> function) and then put it anywhere on your page (or even in a hidden DIV
> that you can show or hide with a mouse click). Then it doesn't trash the
> design of your page.
>
> We never write any output directly to anything now - catching it a
> <savecontent> block lets us position it anywhere - separating layout from
> the the content.
>
> Regards,
> Gary Menzel
>
>
--
E: [EMAIL PROTECTED]
W: www.compoundtheory.com
ICQ: 3094740
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email to
[email protected] with the words 'unsubscribe cfcdev' as the subject of the
email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting
(www.cfxhosting.com).
CFCDev is supported by New Atlanta, makers of BlueDragon
http://www.newatlanta.com/products/bluedragon/index.cfm
An archive of the CFCDev list is available at
www.mail-archive.com/[email protected]
