One of the reasons is that FBX_Settings usually has this: <cfparam name="attributes.fuseaction" value="Login.login">
That won't work until Circuits is defined. -----Original Message----- From: Jeremy Ridout [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 3:35 PM To: '[EMAIL PROTECTED]' Subject: fbx_Circuits first? Question: why does fbx_circuits come before fbx_settings? Here's my dilemma: I have gotten into the habit of creating a structure that contains all of the variables that are needed for the current request. Most are constants, but some may change depending on the nature of the request. For example: request.stMyApp = StructNew(); Regardless of that, I usually define this structure in the first template that is run (before FB, this was Application.cfm or something similar). Now, it seems natural to me to place this bit of code into fbx_settings. However, getting into FB3, I found that in fbx_circuits, I don't like typing out the path. Furthermore, when I move application around, it MAY change directories. Therefore, I want to create a variable that will hold the base path. I would normally do this within the structure described above. For example: request.stMyApp.circuitPath = "blah"; Therein lies the problem... because fbx_circuits comes first, it isn't yet aware of the structure that did/will define in fbx_settings. Therefore rendering fbx_settings to less than a comparable app_globals. The question again: Why? Thanks, Jeremy ==^================================================================ 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 ==^================================================================
