Rick,
Since Greg (the original poster) said that he was using his act_ file like
a custom tag, I assumed -- uh, oh -- that he is actually calling the page
like a custom tag: e.g. <cf_act_nav-trail foo=blah...etc> or with a
CFModule call. If that is the case, then if he wanted to set an
"attributes." scoped variable in the calling template, then within the
custom tag page he would need to set "Caller.Attributes.VarName".
If he isn't actually doing a cfmodule or custom tag call to his act_ file,
then your statement would be valid; he would end up with a variable with
"Caller." scope and his subsequent act_ and dsp_ files aren't likely to
find it if they're looking for "attributes." vars.
Kevin
--------------------------
Kevin Marshall
Certified ColdFusion Developer
eCalton.com, Inc.
Vero Beach, FL
www.ecalton.com
[EMAIL PROTECTED]
561.569.4500
rlamb@hostwor
ks.com (Rick To: Fusebox <[EMAIL PROTECTED]>
Lamb) cc:
Subject: RE: Variable Scoping
11/14/00
03:17 PM
Please
respond to
fusebox
I really don't understand caller.attributes.variable. Maybe somebody could
explain why you would ever do this? Or if it would really work. And on this
topic, is it possible to assign any name for a scope of a variable? Like
myvariables.variable? Cause it seems like this is what you would be doing
by
using caller.attribute.variable. caller would be the scope, attribute would
be your custom named scope, and variable would be the variable name. Am I
just confused here or what?
Thanks,
Rick
-----Original Message-----
From: Fred T. Sanders [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 14, 2000 2:13 PM
To: Fusebox
Subject: Re: Variable Scoping
It would really depend on what you wanted the tag to do.
In your case none of them really apply. As your already using it to set a
persistant variable.
If you were using the tag to update an attribute. scoped variable already
in
place on the calling template/tag it would be
caller.attributes.somevar
If you were using it to update a request. scoped variable (variable that's
alive for the duration of the page request) no caller. is needed as
request.
scoped variable will cross tag boundaries so it would just be
request.somevar.
If the tag is just setting a local variable used by the calling template
then its just caller.somevar.
Hope this helps
Fred T. Sanders
Charlottesville, VA
-------------------------------------------
Programmers don't lie...
They just can't tell time.
----- Original Message -----
From: "Greg Wolfinger" <[EMAIL PROTECTED]>
To: "Fusebox" <[EMAIL PROTECTED]>
Sent: Tuesday, November 14, 2000 2:14 PM
Subject: Variable Scoping
> Hey Guys:
>
> I've just started to research the fusebox methodologies and have found =
> them very helpful. I picked up a copy of the new book when I was at the
=
> developer conference last week. The only part that is really throwing =
> me off is the variable scoping.
>
> It says to use the Attributes and Request scoping for variables. Say I =
> had a action file (act_nav-trail.cfm) that is used like a custom tag to =
> create or append a session variable that keeps track of the users =
> navigation throughout the site.
>
> That action file spits back to the calling template (i.e. the index.cfm =
> file) a variable called navTrail that is then passed to my display =
> (dsp_nav-trail.cfm) file. In the action file should I set the variable =
> to Caller.Request.navTrail or Caller.Attributes.navTrail or just =
> Caller.navTrail?? Thanks, also if you know of any really good visuals on
=
> the web that helps dipict the fusebox scoping methodologies it would be =
> most appreciated.
>
> Best Regards,
>
>
> Greg
>
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
