home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!jvnc.net!yale.edu!ira.uka.de!news.belwue.de!news.uni-stuttgart.de!helpdesk.rus.uni-stuttgart.de!zrzm0111
- From: zrzm0111@helpdesk.rus.uni-stuttgart.de (MUFTI)
- Newsgroups: comp.sys.acorn
- Subject: Re: Applications and RiscOS 3
- Message-ID: <1992Aug27.105107.10376@news.uni-stuttgart.de>
- Date: 27 Aug 92 10:51:07 GMT
- References: <1992Aug25.090948.10337@waikato.ac.nz>
- Sender: news@news.uni-stuttgart.de (USENET News System)
- Organization: User Help Desk, Comp. Cent. (RUS), U of Stuttgart, FRG
- Lines: 24
-
- In article <1992Aug25.090948.10337@waikato.ac.nz> pdenize@waikato.ac.nz writes:
- >
- >The upshot is that in RiscOS 2 if an application does not have a !Sprites then
- >the !Boot is executed. If it still does not have an icon when the directory it
- >is in is opened again, the !boot is executed again (it is not under RiscOS 3).
- >
- >So how can I tell RiscOS - "no you haven't seen this application before" or
- >"OK so I'm the !Boot file running now forget you ever saw me"
- >
-
- 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 ...
-
- so long
- MUFTI
-