Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/5/84; site cvl.UUCP
Path: utzoo!linus!decvax!genrad!panda!talcott!harvard!seismo!umcp-cs!cvl!gyuri
From: gyuri@cvl.UUCP (Gyorgy Fekete)
Newsgroups: net.micro.atari
Subject: (ST) Install-application from menu
Message-ID: <791@cvl.UUCP>
Date: Sun, 1-Sep-85 19:01:05 EDT
Article-I.D.: cvl.791
Posted: Sun Sep  1 19:01:05 1985
Date-Received: Mon, 2-Sep-85 09:24:04 EDT
Distribution: net
Organization: Computer Vision Lab, U. of Maryland, College Park
Lines: 34

Someone posted a question as to what the bloomin' hell is the
install-application thing from the menu for. After a bit of mucking
around with it, this is what I came up with.

There are three ways an application may be installed (No sh*t, Sherlock)
GEM, TOS and Tos taking parameters. There are probably a lot of things going
on when a program gets loaded into memory, but the ones visible to me were
the following.	

In GEM mode, the cursor is not enabled, but the mouse is
In TOS mode it is the other way around (either way, the program may override
   these defaults).
In tos-taking-parameters mode, if you try to click the application, it will
   first ask for the arguments to it (the argv[1], argv[2], etc).

These modes are reflected in the file extensions PRG, TOS and TTP.
You may have noticed that when you run COMMAND.PRG, there is no cursor
initially (unless you have previusly written the appropriate escape sequence
to the VDI interface sometime before you clicked on this application).
So now we know of at least two ways of getting COMMAND to come up with
a cursor (KERMIT too). Either rename in COMMAND.TOS, or change it to TOS mode
with the menu install-application thing.

Now, if I could make all the installations permanent without playing with
the file extensions.

-- 
Gyorgy Fekete --- University of MD, Computer Vision Lab, (301) 454-4526

gyuri@cvl.{ARPA,CSNet}

...seismo  \
...allegra +--  !umcp-cs!cvl!gyuri.UUCP
...brl-bmd /