Oh, I agree with you there, John. I am hoping that somewhere down the track, the parent circuit won't necessarily be located at ".."
Of course, when that happens, perhaps we'll get an extra API variable or two, like "fusebox.parentlocation", so that the old tricks will still work ;-) Thanks, guys, LeeBB -----Original Message----- From: John Quarto-vonTivadar [mailto:[EMAIL PROTECTED]] Hey Hal, you left out another benefit: By using SuperQ() (which is all of 8 characters), you can have a child refer to its parent *without* knowing anything about the parent. That is, the idea of some hardcoded FB1 trick of "../" can be left aside . That's one of the primary advantages of all of FuseQ is that it removes the physical file dependencies of the circuits and therefore, of the the fuseactions and fuses. IMPORTANT NOTICE: This e-mail and any attachment to it is intended only to be read or used by the named addressee. It is confidential and may contain legally privileged information. No confidentiality or privilege is waived or lost by any mistaken transmission to you. If you receive this e-mail in error, please immediately delete it from your system and notify the sender. You must not disclose, copy or use any part of this e-mail if you are not the intended recipient. The RTA is not responsible for any unauthorised alterations to this e-mail or attachment to it. ==^================================================================ 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 ==^================================================================
