Yes, even in this case it makes sense (to me) to put the return in the switch. Just like how certain fuseactions have 'exit fuseactions', certain fuseactions have 'return fuseactions'. A return fuseaction is simply a dynamic exit fuseaction, the exit fuseaction is simply determined at runtime.
The classic example is plugging in a login script. Fuseaction 1 is a login form, Fuseaction 2 is a login validation. If they are valid fuseaction 2 performs a 'return fuseaction'. Another example is plugging in a survey. Fuseaction 1, 2, 3, 4 are forms for the user to fill out about the survey, passing a WDDX packet between them. Fuseaction 5 saves all of that data to the database then performs a 'return fuseaction'. I'm sure there are plenty of other ways to do this, but this is a method that has worked for me for years. Steve Nelson John Quarto-vonTivadar wrote: > I was talking about the fuseaction that was just completed, not the one to > be returned to. The fuseaction just completed is *typically* an ACT (the > user does something, in MVC it's a C, or the app does something, in MVC it's > a M) but it doesn't have to be; one can certainly have it be a DSP, and if > so there is potential content that may or may not be needed that can be > passed alone. Just like if it had been an ACT and it set a var, MyVar=TRUE, > which one decided to pass along to the next fuseaction; here the content is > available as #fusebox.layout# > > ----- Original Message ----- > From: "Lee Borkman" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, April 26, 2002 6:45 AM > Subject: Re: Returnfuseaction > > I don't think that's quite how it works, John, > > CF_ReturnFuseaction returns to a fuseaction (who would have guessed?). It > doesn't return to a particular line of code. So all the trappings, > settings, layouts, etc associated with that return fuseaction work just the > same way they usually do. > > I think. > > LeeBB > > ----- Original Message ----- > > From: John Quarto-vonTivadar > > We're talking about the question 'when do I return to the fuseaction that > CF_ReturnFuseaction is saving for me?', right? > > Don't you lose your layouts by putting it in the switch, John? If there is > something inside CF_ReturnFuseaction to return to, then it cflocates to > it, > so any preceeding output would get killed. I think a better place would > be > inside the index.cfm file, right after the call to the core file. That > way, > you're completely done with the fusebox and you can cflocate *and* still > do > something with the preceeding output if need be. > > ----- Original Message ----- > From: "John Beynon" <[EMAIL PROTECTED]> > > > i use it in my switch...not sure if that's the best way - but it works > for > > me :) > > > > john. > > > > -----Original Message----- > > From: Roel van der Hoeven [mailto:[EMAIL PROTECTED]] > > > > > > Quick (maybe stupid) question... where would oyu guys put the > > returnfuseaction? The switch or the page called by the fuseaction? > > > > TIA Roeligan > ==^================================================================ 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 ==^================================================================
