It wouldn't appear at all, Bob. That sort of variable is up to the developer and is independent of the fuse's role in the application. Since the variable is not passed out of the fuse, the rest of the system could care less what it's about.
There are occasional questions about walking on other variables, but if the fuse is properly documented, the developer is aware of other variables that exist when the fuse operates, so he won't walk on anything important. - Jeff On Tuesday, May 7, 2002, at 01:18 PM, Bob Krieger wrote: > OK... Within the FuseDoc itself, we can define input and output > variables. They can be defined as such: > > <fusedoc> > ... > <io> > <in> > <string name="StringVar" scope="attributes" /> > </in> > <out> > <string name="StringVar" scope="form" /> > </out> > </io> > </fusedoc> > > OK, what if you have a "variables" scoped variable, generated within > that fuse for use only within that fuse, such as a counter or some > such? Where would that be defined? > I can hazard a guess... How about within the <io> tags but not > within either the <in> or <out> tags? > > I'm trying to get the parameters down. Thanks, loads! > > Bob Krieger > www.fbtutor.com > The FuseBox Tutor > > > ==^================================================================ 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 ==^================================================================
