At 11:10 PM +0100 23/8/1999, Dave Cragg wrote:
>>The way I always do it is to put the external in the same directory as the
>>executable. When in non-standalone mode, thats the MetaCard program folder,
>>when a standalone, the same directory as the app itself. Then add it to the
>>Externals property.
>>
>
>That's what I thought, but when I tried it, the external commands
>weren't recognized in the standalone. (This is with Win NT 4.0 and
>MC 2.2.4) That's what prompted me to look at the $PATH variable. In
>the standalone, it didn't include the path to the executable, only
>the paths to the WinNT folder and the System32 folder. (Is this how
>it should be?) When I added the above script in the startUp handler,
>it worked fine.
I took a look at this again. It was a little strange. The externals
property is set for the main stack, which is the stack from where the
external commands are issued. Attached to the main stack is a
substack which opens in the window of the main stack. If the substack
is opened, and then the main stack is returned to, again in the same
window, the external command isn't recognized. It works fine if the
external command is issued before the substack ever opens.
The problem doesn't occur when the main stack and substack are opened
in their own windows.
This sounds like there is a mysterious (to me) relationship between
stacks and windows. However, I now have a pattern to the behaviour
and can work around it. Thanks again for the help, Kevin.
Cheers
Dave Cragg
_____________________________________________
The LACS Centre (Business English Training Resources)
mailto:[EMAIL PROTECTED]
http://www.lacscentre.co.uk
_____________________________________________
