home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!wupost!waikato.ac.nz!aukuni.ac.nz!cs18.cs.aukuni.ac.nz!jwil1
- Newsgroups: comp.sys.acorn
- Subject: Re: Applications and RiscOS 3
- Message-ID: <1992Sep1.042404.13341@cs.aukuni.ac.nz>
- From: jwil1@cs.aukuni.ac.nz (TMOTA)
- Date: Tue, 1 Sep 1992 04:24:04 GMT
- Sender: jwil1@cs.aukuni.ac.nz (TMOTA)
- References: <1992Aug25.090948.10337@waikato.ac.nz> <1992Aug27.105107.10376@news.uni-stuttgart.de>
- Organization: Computer Science Dept. University of Auckland
- Lines: 27
-
- zrzm0111@helpdesk.rus.uni-stuttgart.de (MUFTI) writes:
-
- >I don't know, if this idea fits to your problem, but you can easily forbid
- >to execute the commands in the bootdir:
-
- >*if "<application$boot>"="" then execute command1 of bootdir
- >*if "<application$boot>"="" then execute command2 of bootdir
- >...
- >...
- >*if "<application$boot>"="" then execute commandN of bootdir
- >*if "<application$boot>"="" then set application$boot whatever
-
- >This sollution is not the fastest ...
-
- Wouldn't the following be a lot better...?
-
- *if "application$boot>"="" then Obey <Obey$Dir>.!DoBoot
-
- (and in "!DoBoot"):
- | all the commands originally in the !boot, and...
- *set application$boot whatever
-
- Much tidier...
- --
- _________________ "I'd like to answer this question in two ways:
- /____ _ _/_ __ First in my normal voice, and then
- // / //_//_ /_/ in a silly, high-pitched whine." (Monty Python)
-