Thanks Chipp and Brian... I think I didn't clarify very well.
 
'the externals' can easily be set, using relative or calculated paths. This is not a problem. What I find strange is that the stack has to be closed and re-opened for the externals to 'fix' and so make the externals available for use.
 
I discovered that we can "set the externals of stack tStackFilePath to tExternalFilePath" from another stackFile. When opened, tStackFilePath works on first time launch.
 
Perhaps a sub-stack can have its externals set when the mainStack launches, and when the subStack opens it is ready to go. Dunno. I'll try this approach also.
 
/H
 
 
In a message dated 24/09/2004 17:04:04 GMT Daylight Time, [EMAIL PROTECTED] writes:
From: Brian Yennie <[EMAIL PROTECTED]>
Subject: Re: easy externals question
To: Discussions on Metacard <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; format=flowed

I would try setting a relative path to your externals- then there
should be no need to reset the paths. Or is there a reason that you
would need to change even the relative path?

> That's silly. How does RunRev get around it? Or  do they just assume
> we don't
> use an external until the next  session?
 
Hugh Senior
The Flexible Learning Company
Web: www.FlexibleLearning.com
E: [EMAIL PROTECTED]
T/F: +44(0)1483.27 87 27
_______________________________________________
metacard mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/metacard

Reply via email to