Evan Wilders wrote:
> I was having
> a lot of trouble properly passing complex variables
> around.
That's where an inter-fuse variable scope comes in. Reserve the base
variables scope for stuff that is local to a given fuse, and put stuff
like XFAs, qry_ recordsets, and so on in a pseudo-scope... I use
"fusebox". When you need to CFMODULE your way to another fuseaction,
just use something like:
<cfmodule template="index.cfm" fusebox="#fusebox#">
Then, at the top of app_globals or the FB3 equivalent, drop in:
<fif IsDefined("attributes.fusebox")>
<cfset fusebox = Duplicate(attributes.fusebox)>
</cfif>
At that point, recursive variable handling becomes pretty much
transparent.
--
Roger
==^================================================================
This email was sent to: [email protected]
EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9
Or send an email to: [EMAIL PROTECTED]
T O P I C A -- Register now to manage your mail!
http://www.topica.com/partner/tag02/register
==^================================================================