Topic : Documentation for Thing
Author : Arno Welzel/Thomas Binder/TransAction
Version : thing.hyp 1.27E (23/8/1998)
Subject : Documentation/Shells
Nodes : 269
Index Size : 6336
HCP-Version : 4
Compiled on : Atari
@charset : atarist
@lang :
@default : %I
@help : %Hilfe
@options : +g -i -s +y +zz -t4 -d10
@width : 75
@hostname : THING
View Ref-FileExtra - Applications... (Options) Thing
This page allows each program to be individually configured to suit your
working environment:
Compare full pathname: Normally all settings for installed applications are valid only if the program is launched from exactly the same
directory. If this option is deactivated (uncrossed) then the same
program name will suffice, as the path is disregarded.
An example: If one installs 'C:\INTERNET\CAB.APP' as an application the
settings are originally valid only if 'C:\INTERNET\CAB.APP' is started.
If one then moves the program file to another directory, say to
'C:\INTERNET\BROWSER\CAB.APP', the settings for CAB will suddenly be
disregarded because the path has changed. By deactivating the 'Compare
full pathname' option we can now ensure that the settings are valid for
all programs with the filename 'CAB.APP', no matter what directory they
are in.
If one has selected 'Application' as the 'Start directory' on the
'General' page of this dialog, then naturally the settings of the just
lauched application will be set, not the installed one.
Auto-start on booting: The application is started automatically on
launching Thing (normally immediately after booting the system).
Ask for parameters on starting programs: If this option is active (crossed)
the program asks for command line parameters if it is started 'directly'
without passing the file or pathname as parameters (for example via
Drag&Drop on the program icon, or for Opening/Showing/Printing a file
with an appropriate the program).
Understands VA_START: If this option is active (crossed) Thing uses
VA_START messages for passing parameters between currently active GEM
applications or accessories.
When inactive, accessories are sent the AC_OPEN message, while programs
will always undergo multiple starts (following a query dialog).
TOS programs (TOS, TTP) ignore this option as they cannot react to AES
messages.
Unload Thing from memory before starting programs: Before starting the
program Thing is removed from memory, freeing up extra memory that is
then free for the program itself to use, and the program is started by
the small ThingRun utility; this remains memory resident ready to take
over and reload Thing on exiting the program.
This option is now also available under multitasking OSs. However,
problems are likely to arise with the AV Protocol, as the AV-server is
suddenly no longer active and with MultiTOS etc. can quite easily have a
different application-ID after a 'revival', causing AV clients to send
their messages to the wrong program.
In addition, under MultiTOS, N.AES prior to version 1.1.7, Geneva etc.
Thing can no longer be started as a system shell, which -- depending on
the OS -- can result in more or less visible redraw errors, although
this has no negative effects on the actual operation.
Execute in Single mode: This option starts programs in Single mode under
MagiC. This mode can also be used for programs which output directly to
the screen and not into a GEM window. As a side-effect, Thing is
completely removed from memory before starting the program, which frees
up the maximum memory. However, desk accessories are 'frozen out' in
Single mode.
This option is only effective if Thing is installed as a shell under
MagiC (using the #_SHL entry in MAGX.INF).
Run in Console window, if necessary: If this option is active (crossed)
TTP/TOS programs can be executed in a Console window (similar to Gemini
with Ease). The Thing Console window, called TOS2GEM, programmed by
Thomas Binder, must be installed for this.
This option is ignored by GEM applications and desk accessories.
Wait for keypress: If this option is active (crossed) Thing waits for
a keypress after exiting TOS/TTP programs before the Console window is
closed, or before the desktop is set up again.
This option is ignored by GEM applications and desk accessories.
Memory limit: Here one can specify the maximum amount memory in kilobytes
a program may occupy, including all memory blocks allocated at run-time.
This setting is effective under MultiTOS, N.AES and MagiC 4 onwards.
Memory limitation is sensible above all for older programs that try to
grab all available memory (First Word Plus etc.) as they are made to
believe that less free memory is available -- namely that specified here
-- so that they cannot allocate more than this.