Yes, but that won't deal with the situation where the parent's variables set in FBX_Settings were overridden by the child. Or the child overrode some of the settings of the grandparent. H.L. Mencken put it best, "For every complex problem, there's an answer that's simple, obvious...and wrong."
-----Original Message----- From: Lee Borkman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 21, 2002 5:56 PM To: [EMAIL PROTECTED] Subject: SuperQ functionality with the STANDARD core (Re: MVC question) Hi guys, There is a simple way to invoke the parent circuit's fuseaction using the standard core files. I have been doing this as a matter of routine for a long time now... All you need to do is create the child circuit's <cfdefaultcase> so that it cfincludes "../fbx_switch.cfm". It's about as simple and efficient as you could get. If you want the child to "override" with its own version of the fuseaction, then create the fuseaction in the child, and the defaultcase will not be invoked. If you want the parent's functionality, then don't create the fuseaction in the child, and the default will be invoked, so the parent gets the call. The standard core is VERY powerful ;-) thanks, LeeBB ----- Original Message ----- ----- Original Message ----- From: "Jeff Peters" <[EMAIL PROTECTED]> > That's what the SuperQ() function is about. You can place the > fuseaction in the parent of the three, then call it by: > SuperQ(fuseaction) > > - Jeff > > On Tuesday, May 21, 2002, at 01:45 PM, craig girard wrote: > > > I have a question concerning MVC I am hoping someone might be able to > > shed > > some light on. In the example documentation on techspedition.com Hal > > shows > > there being three roles for using the fictional site. Those roles are > > Admin/CSR/Guest. > > > > He also shows there being three controller directories , one for each > > role. > > > > What I am curious about is, what do you do when you have a fuseaction > > that > > all three roles can use exactly the same? Do you replicate this > > fuseaction > > across each controller? That would seem inefficiant. Would you place > > the > > fuseaction in the Guest controller and have the other two access this > > fuseaction from there? If so, how does the flow for this work. > > > > I am lazy and trying to get out of replicating logic that is used by all > > user roles. What is the best way to go about this? > > > > Thanks, > > > > Craig > > > > > ------=_NextPart_000_007B_01C20166.189F9A00-- ${list_promo} ${list_promo} ==^================================================================ 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 ==^================================================================
