No, because the top fusebox doesn't strip anything away. Using ListLast on
the fuseboxes lets me use them either in stand-alone mode or as nested
fuseboxes. These two formulations:
ListFirst(xxx.someValue,'.') and
ListFirst(someValue)
return the same thing: someValue.
-----Original Message-----
From: Chris Bartley [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 09, 2000 12:13 PM
To: [EMAIL PROTECTED]
Subject: RE: sub-fuse
Why don't they all use ListFirst()? Wouldn't there only be only 1 item in
the list (the fuseaction) once it gets down to the nested fuse anyway?
At 2:38 PM -0700 8/9/00, Hal Helms wrote:
>Here's what I do:
>
>Each fusebox uses a fuseaction with the format xxx.someFuseaction, where
xxx
>is a unique identifier. For example, if you were working with a shopping
>cart, you might have fuseactions like crt.emptyCart.
>
>Each nested fusebox uses this to get the appropriate fuseaction.
>
><cfswitch expression = "#ListLast(attributes.fuseaction,'.')#">
>
>Then the cfcase values are the fuseaction less the prefix. Example:
>emptyCart.
>
>The outer fusebox uses <cfswitch expression =
>"#ListFirst(attributes.fuseaction,'.')#">
>
>And checks for case values like this:
>
><cfcase value = "crt">
> <cfinclude template = "ShoppingCart/index.cfm">
>
>I find it works very nicely.
>
>Hal
----------------------------------------------------------------------------
--
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.
