That's cool, Ralph. I've done it in the past. There becomes a trade-off
between having one honkin' piece of code used by multiple fuseactions and
having discreet, smaller files. It's a style issue, but I'd be wary of
making the cfif fuseaction thing a common occurance.
NAT
-----Original Message-----
From: Huffnagle, Ralph [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 27, 2000 8:39 AM
To: Fusebox
Subject: Using fuseaction in <CFIF>
I have been using statements like the following in some of dsp files:
<cfif attributes.fuseaction eq "Action1">
<td>#display1#</td>
</cfif>
Everytime I do it, I get the feeling that I shouldn't be. Is there anything
wrong with using attributes.fuseaction in a <CFIF>? I am trying to reuse
dsp files, but the one fuseaction needs to show one more piece of
information.
Thanks,
Ralph
----------------------------------------------------------------------------
--
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.
------------------------------------------------------------------------------
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.
