HELP nit and suggestion

  • This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.
#1
Help topic "autobatch.btm"

The topic does not mention the simple ways to suppress using TCSTART: /I or
/IS command options or the StartupFile=No directive.

BTW, is the only directory searched for TCSTART and for TCEXIT the one
containing the program when a path is not specified?

Suggestion:
Add controls to the OPTION dialog, STARTUP page, to set the StartupFile and
ExitFile directives.
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
10,210
86
#2
Help topic "autobatch.btm"

BTW, is the only directory searched for TCSTART and for TCEXIT the one
containing the program when a path is not specified?
Yes - see the "TCSTART and TCEXIT" topic in the help.

Suggestion:
Add controls to the OPTION dialog, STARTUP page, to set the StartupFile and ExitFile directives.
Those directives are obsolete and only maintained for backward compatibility.
 
#3
rconn wrote:
| ---Quote (Originally by Steve Fábián)---
|| Suggestion:
|| Add controls to the OPTION dialog, STARTUP page, to set the
|| StartupFile and ExitFile directives.
| ---End Quote---
|
| Those directives are obsolete and only maintained for backward
| compatibility.

They are very useful for applications that are not interactive; also
occasionally for "piped to" instances. AFAIK TCStartPath is examined only
when a TCC instance starts, so ExitFile is the only dynamic control for
TCEXIT execution (short of fooling around with the file system itself), esp.
since the /IS command option does not affect TCEXIT execution either. Please
retain them!
--
Steve