In <001c01bfb9d3$99277080$28681fd1@certisource>, B.Cravens
([EMAIL PROTECTED]) in a fit of unbridled passion, wrote:
> You have it a little flip-flopped.
>
> To make variables available to the custom tag, pass them as attributes of
> the custom tag. The caller scope is used inside of the custom tag to pass
> any values back to the calling page. Then those variables are available as
> local (Variables) scope variables.
>
> For example, the below example would output "value2"
There are many uses for accessing variables in the caller scope other
than simply writing results. Application globals defined in your
application.cfm file is one way that I often need to use caller. scope.
But, for passing settings into a custom tag FOR that custom tag, yes --
you should use the attributes. scope as shown below:
>
> <!---your calling page--->
> <cf_yourcustomtag variable1="somevalue">
> <cfoutput>
> #testvar#
> </cfoutput>
>
>
> <!---your custom tag --->
> <cfset caller.testvar = "value2">
> <cfset testvar = "value1">
>
Your forgot to put in the <cfparam name="Attributes.variable1"> to
demonstrate how to access the variables passed in the <cf_yourcustomtag>
statemnet.
HTH,
-R
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
