Re: applying child layout only

[Lee Borkman]

What exactly do you want, Kay?  You want the child layout, but NOT the parent, and then you still want the grandparent layout?  Or do you just want the child layout and nothing above that?   If it's just the child layout and nothing else, then you can just set attributes.suppresslayout at the end of the child's fbx_layouts.  Make sure all your other fbx_layout files pay attention to that flag.   If you want to skip the parent layout only, then that's a little trickier.  Perhaps, in that case, you should really consider of the child is REALLY a child pof the parent, or if it should be a sibling instead, because the layouts are nutually exclusive, which doesn;t really suggest a child-parent relationships.   But if you are happy that child-parent is really the way it should be, then you can create a skiplayout flag, or even a skiplayout as a number to say exactly how many layouts to skip.   Here is a snippet from another conversation I had recently about this same question.   Perhaps it's the kind of thing you are looking for.   Let us know how you go.   See ya, Leebles   -------------------------------------------------------------------   How about this in the Child.Birthday fuseaction:   <cfcase value="birthday">   <cfinclude blah blah>   <cfinclude blah blah>   <cfset attributes.skiplayout="true"> </cfcase>     Now, all we need is to write fbx_layouts that handle this #attributes.skiplayout# flag:   <cfparam name="attributes.skiplayout" default="false"> <cfif attributes.skiplayout and NOT fusebox.isTargetCircuit>   <cfset fusebox.layoutfile="">   <cfset attributes.skiplayout="false"> <cfelse>   <cfset fusebox.layoutfile="lay_normal.cfm"> </cfif> <cfset attributes.skiplayout="false">   Now, that doesn't require circuits to have any knowledge of each other.  It only requires that you choose to use a particular flag called #attributes.skiplayout#.  You could even make a #attributes.skiplayout# hold a number, so you can define how many layouts you want to be skipped.  Now, I'm not saying that this is a great idea, because it assumes that your child knows something about the higher-level layouts, but perhaps you get an idea of the kind of information tha circuits can pass to each other, without having to know any detailed information about each other.   You will find that both the Child and Parent circuits would be completely portable into any application that used the #attributes.skiplayout# flag, without any modification at all, because the circuits don't assume anything about each other.  Instead, the circuits tell each other what they need to know.  In this case, the Child.Birthday fuseaction tells all the other circuits that it does not want the Circuit above (note that it doesn't know anything about the circuit above) to add any layout.  The Parent circuit has access to this information, only because the Child circuit has explicitly supplied it, and the Parent circuit knows nothing else about the Child circuit, but it has been told everything it needs to know, ie no layout from the circuit above.   ----------------------------------------   ----- Original Message ----- From: Kay Smoljak Hi all, What do I do if I want to apply the child layout for a child circuit, but don't want the parent layout to be applied afterwards? I thought that was covered in the FB3LayoutApp example, but it doesn't seem to be. Right now I'm using an attributes.suppresslayout flag to apply all layouts or none. ==^================================================================ This email was sent to: archive@jab.org 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 ==^================================================================