Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!gatech!udel!mmdf From: STU00@vx.acss.umn.edu (Stuart Stanley) Newsgroups: comp.sys.amiga Subject: Installbeep ideas Message-ID: <19643@louie.udel.EDU> Date: 13 Jul 89 18:19:50 GMT Sender: mmdf@udel.EDU Lines: 45 Hello all, After playing with installbeep last night, (Very impressive) I think I figured out an addition that might be, er, fun. Here it is: 1) Allow multiple sounds files on the command line. (or maybe a file that contains a list of sounds) 2) The program would then load 1 sound file (Thus saving memory) and then wait for a beep command. 3) When a beep arrives, it would do that sound and then begin loading a random second sound from the list. If another beep comes in before the new sound is loaded, it would use the old one. Otherwise it would finish, dispose of the first sounds memory and go back to 2. *note* If a sound file can't be opened, it is 'x'ed off the list and another is tried. A little check should detect the absence of any sounds. This could prompt a requester saying sound files missing or just default the program to 'beep' mode. I would think that this would be kind of a fun option. You could specify a whole directory full of sounds and get a different one each time you make a mistake. What does everyone think? In particular, what does the Author think. (Are you cringing in horror at the thought or is this a possible idea). Cheers, / - - - - - - - - - - - - - - - - - - - - - - - - - - - - v - - - - - - - \ | x Stuart Stanley | " " | | x STU00@UMNACVX.BITNET | O O | | x x | xxxxxxxxxx | | x "Sing to me, my angel of music" - The Phantom | xxxxxxxxxx | | "Gulp" - Dungeon Master | / \ / \ | | | ^ ^ ^ ^| \ - - - - - - - - - - - - - - - - - - - - - - - - - - - - ^ - - - - - - - /